Shared Memory MCP Server

Cross-agent persistent memory store. Deploy once, connect any MCP-compatible agent.

Tools

Tool	Description
mem_add	Save a memory with category, tags, and agent name
mem_search	Search by keyword, tag, or category (hybrid vector + keyword when EMBEDDING_API_KEY is set)
mem_list	List recent memories
mem_get	Get a specific memory by ID
mem_update	Update an existing memory's content, category, tags, or agent (re-embeds on content change)
mem_delete	Delete a memory by ID
mem_stats	View memory store statistics

Connect any MCP agent

Claude Code

Add to .mcp.json in your project root:

{
  "mcpServers": {
    "shared-memory": {
      "url": "https://YOUR_DEPLOYMENT_URL/mcp"
    }
  }
}

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "shared-memory": {
      "url": "https://YOUR_DEPLOYMENT_URL/mcp"
    }
  }
}

Hermes Agent

Add to config.yaml:

mcp_servers:
  shared-memory:
    url: "https://YOUR_DEPLOYMENT_URL/mcp"
    transport: streamable-http

Any MCP-compatible agent

Point to https://YOUR_DEPLOYMENT_URL/mcp with Streamable HTTP transport.

Environment Variables

Copy .env.example to .env and fill in:

Variable	Description	Required
SUPABASE_URL	Supabase project URL	Yes
SUPABASE_ANON_KEY	Supabase anon (public) key	Yes
MCP_API_KEY	Shared secret to gate the /mcp endpoint. Clients pass it via ?key=..., X-API-Key:, or Authorization: Bearer .... If unset, the endpoint is unauthenticated.	No
EMBEDDING_API_KEY	OpenRouter API key. Enables hybrid vector + keyword search via openai/text-embedding-3-small.	No

Auth & threat model

The deployed /mcp endpoint accepts a MCP_API_KEY as a bearer token, header, or query param. The query-param form is convenient for MCP clients that only accept a URL, but it leaks into proxy/server logs — treat the full URL (including ?key=...) as a secret, store it the same way you'd store a password, and rotate via your Vercel env if it's exposed. Without MCP_API_KEY set, anyone who finds the deployment URL can read and write your memory store.

Deploy to Vercel

vercel --prod

Set env vars in Vercel dashboard or via CLI:

vercel env add SUPABASE_URL
vercel env add SUPABASE_ANON_KEY

Run locally

cp .env.example .env  # then fill in SUPABASE_URL and SUPABASE_ANON_KEY
node --env-file=.env --experimental-strip-types server.mts

License

MIT