getmnemo-mcp

Model Context Protocol server for Mnemo Memory — exposes long-term memory tools to any MCP client (Claude Desktop, Cursor, Windsurf, VS Code, Zed).

Tools

| Tool | What it does | |---|---| | memory_search | Hybrid 7-strategy retrieval over the workspace memory store. | | memory_add | Store an atomic fact with optional metadata. | | memory_update | Patch an existing memory's content or metadata. | | memory_delete | Permanently remove a memory by ID. | | memory_list | Paginate through memories (cursor-based). |

All calls are scoped to a workspace and a tenant container, both supplied by the operator at server startup (env). The container is the tenant boundary — it is not an argument the model can set; the tools only take content/query.

Install

Claude Desktop / Cursor / Windsurf / VS Code / Zed

npx -y getmnemo-mcp

Or wire it into the client config directly. Example for Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "getmnemo": {
      "command": "npx",
      "args": ["-y", "getmnemo-mcp"],
      "env": {
        "GETMNEMO_API_KEY": "prfly_live_...",
        "GETMNEMO_WORKSPACE_ID": "ws_...",
        "GETMNEMO_CONTAINER_TAG": "user:jane"
      }
    }
  }
}

Get an API key at https://app.mnemohq.com/settings/api-keys.

Develop

npm install
cp .env.example .env   # fill in GETMNEMO_API_KEY + GETMNEMO_WORKSPACE_ID + GETMNEMO_CONTAINER_TAG
npm run dev            # stdio
npm run dev:http       # HTTP/SSE on :8787
npm run build          # bundle to dist/

Architecture

• stdio (src/cli.ts): one process per MCP client connection, env-configured.
• HTTP/SSE (src/http.ts): single long-running process for hosted use, header-or-OAuth auth.
• Both transports share src/server.ts (tool registration + dispatch) and src/api-client.ts (typed REST wrapper).

The server deliberately does NOT depend on getmnemo (the JS SDK) so it can ship independently.

License

MIT