mempalace-mcp-proxy
v1.0.3
Published
Cursor stdio MCP proxy to memory API (Streamable HTTP) with MEM_X-User-Id; legacy debug server via MEM_LEGACY_DEBUG_SERVER=1.
Maintainers
Readme
mempalace-mcp-proxy
Local stdio MCP proxy that forwards Cursor-style clients to an upstream Streamable HTTP MCP service while injecting workspace and VCS context.
Metadata injection is tool-scoped, not global. The current whitelist is:
add_memorysearch_memory
Other tools are forwarded without injected project metadata.
Structure
src/bin/- executable entrypoints
src/core/- shared runtime helpers
src/context/- request/header construction and client-context collection
src/proxy/- upstream MCP proxy implementation
src/vcs/- git/svn/workspace inspection
src/legacy/- old debug-server helpers kept behind
MEM_LEGACY_DEBUG_SERVER
- old debug-server helpers kept behind
src/ root stays directory-only. Import modules through the structured
subpaths instead of root-level compatibility wrappers.
The package now exposes stable subpaths through package.json.exports, for
example:
const { getUpstreamMcpUrl } = require("mempalace-mcp-proxy/context/proxy-env");
const { inspectVcsAtWorkspace } = require("mempalace-mcp-proxy/vcs/workspace-vcs");Run
Local dev (same entry as the published CLI):
npm startPublished package / one-shot (bin name matches package.json name):
npx -y mempalace-mcp-proxynpx -y mempalace-mcp-proxy installs the package and runs the mempalace-mcp-proxy bin. A second bin name mcp-npx-server points to the same file for older configs.
Publish
This package is plain CommonJS JavaScript. There is no TypeScript build step or separate compile artifact.
npm install
npm run check
npm run pack:dry-run
npm run publish:npm