Cursor, VS Code & Windsurf

For AI Agents

Machine-readable docs: mnemoverse/llms.txt (works in all sandboxes)

Give your code editor persistent memory. One config file — it remembers across sessions.

Get your API key at console.mnemoverse.com (free tier, no credit card).

If you already have a key from Claude Code or ChatGPT — use the same one. That's the point.

VS Code + GitHub Copilot Chat Agent Mode

Status (2026-05): the dedicated Mnemoverse Memory VS Code extension is not yet published to the Marketplace or Open VSX. Until it ships, use the manual .vscode/mcp.json config below — it works identically for Copilot Chat Agent Mode (VS Code 1.102+) and for any other VS Code AI extension that consumes MCP servers.

Chat client	Install path
VS Code + Copilot Chat — Agent Mode	Manual .vscode/mcp.json (see below)
VS Code + Copilot Chat — Ask / Edit Mode	Not supported — MCP servers only run in Agent Mode
VS Code — any other MCP-consuming extension	Manual .vscode/mcp.json (see below)
Cursor	.cursor/mcp.json (see Cursor section below)
Windsurf	~/.codeium/windsurf/mcp_config.json (see Windsurf section below)

When the extension lands, this section will switch back to a one-click install path. Track github.com/mnemoverse/mnemoverse-vscode for status.

Manual JSON config (Cursor, VS Code, Windsurf)

Cursor — add to .cursor/mcp.json:

{
  "mcpServers": {
    "mnemoverse": {
      "command": "npx",
      "args": [
        "-y",
        "@mnemoverse/mcp-memory-server@latest"
      ],
      "env": {
        "MNEMOVERSE_API_KEY": "mk_live_YOUR_KEY"
      }
    }
  }
}

VS Code — add to .vscode/mcp.json (note: VS Code uses servers, not mcpServers):

{
  "servers": {
    "mnemoverse": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@mnemoverse/mcp-memory-server@latest"
      ],
      "env": {
        "MNEMOVERSE_API_KEY": "mk_live_YOUR_KEY"
      }
    }
  }
}

Windsurf — add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "mnemoverse": {
      "command": "npx",
      "args": [
        "-y",
        "@mnemoverse/mcp-memory-server@latest"
      ],
      "env": {
        "MNEMOVERSE_API_KEY": "mk_live_YOUR_KEY"
      }
    }
  }
}

⚠️ Restart your editor after editing the config file. MCP servers are only picked up on client startup.

Why @latest? It forces a registry metadata lookup on every session start so you always get the newest release — bare npx @mnemoverse/mcp-memory-server caches the first installed version indefinitely.

Try It

Say to your editor AI:

"Remember that I always deploy to Railway using railway up"

Then in a new session:

"Deploy this project"

It remembers.

Tools

The MCP server gives your editor 6 tools:

Tool	What it does
memory_write	Store a preference, decision, or lesson
memory_read	Search memories by natural language query
memory_feedback	Report if a memory was helpful (+1) or wrong (-1)
memory_stats	Check how many memories are stored
memory_delete	Permanently delete a single memory by its id
memory_delete_domain	Wipe all memories in a domain (requires explicit confirm)

For detailed parameter docs, see Claude Code & Desktop or API Reference.

Universal Memory

Same API key, same memories — across all tools.

                    ┌── Claude Code / Desktop
   Mnemoverse API ──├── Cursor / VS Code / Windsurf ← you are here
   (one memory)     ├── ChatGPT (Custom Actions)
                    └── Python SDK / REST

Write a memory in Cursor → Claude Code reads it. Learn something in VS Code → ChatGPT knows it.

Configuration

Variable	Required	Default
MNEMOVERSE_API_KEY	Yes	—
MNEMOVERSE_API_URL	No	https://core.mnemoverse.com/api/v1

Source & Distribution

The MCP server is also listed on the Official MCP Registry — any MCP-aware client that browses the registry will find it there. Source code is open on GitHub under MIT.

Related

• Claude Code & Desktop — Claude integrations
• ChatGPT — give any Custom GPT persistent memory
• Python SDK — for scripts and backends
• API Reference — full endpoint documentation