MnemoverseDocs

Appearance

Cursor ​

For AI Agents

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

Give Cursor persistent memory. One config entry — the agent remembers across sessions, projects, and even other tools.

You'll need an API key — get one free at console.mnemoverse.com (no credit card). If you already have a key from Claude Code, VS Code, or ChatGPT — use the same one. That's the point.

Add to Cursor ​

Cursor — click to install, or add to .cursor/mcp.json:

Add to Cursor

json
{
  "mcpServers": {
    "mnemoverse": {
      "command": "npx",
      "args": [
        "-y",
        "@mnemoverse/mcp-memory-server@latest"
      ],
      "env": {
        "MNEMOVERSE_API_KEY": "mk_live_YOUR_KEY",
        "MNEMOVERSE_API_URL": "https://core.mnemoverse.com/api/v1"
      }
    }
  }
}

⚠️ Restart Cursor 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.

Keyless options ​

The keyless Mnemoverse Memory extension is also on Open VSX and works in Cursor — install, click Sign In, done.

Remote OAuth ​

Prefer no key at all? Cursor's native OAuth (cursor://) is permitted by the hosted connector's sign-in allowlist: add a remote MCP server pointing at https://mcp.mnemoverse.com/mcp and sign in via the browser — no API key to paste. See which clients can sign in. If OAuth doesn't complete on your setup, the .cursor/mcp.json config above always works.

Try It ​

Make Cursor's AI actually use Mnemoverse

Connecting adds the memory tools; it doesn't make the assistant use them. By default it answers from its own context, not Mnemoverse. Set a one-line standing instruction first: Make Your Agent Use Memory.

With that in place, the win is one memory across tools. In Cursor:

"Remember: this repo's migrations run with make db-migrate, never prisma migrate directly."

Later, in Claude Code or ChatGPT — a different tool:

"How do I run migrations here?"

It recalls the rule, because the memory lives in Mnemoverse, not in Cursor. (A same-tool "it remembers" demo wouldn't prove much — cross-tool recall is what needs Mnemoverse.)

Tools ​

The MCP server gives Cursor 7 core memory tools:

ToolWhat it does
memory_writeStore a preference, decision, or lesson
memory_readSearch memories by natural language query — optionally newest-first (order_by) or time-bounded (since / until)
memory_list_recentList newest memories first, no query — catch up after a break or on a shared room
memory_feedbackReport if a memory was helpful (+1) or wrong (-1)
memory_statsCheck how many memories are stored
memory_deletePermanently delete a single memory by its id
memory_delete_domainWipe all memories in a domain (requires explicit confirm)

For detailed parameter docs, see Claude Code or API Reference. Shared rooms (Beta) — a memory pool shared across accounts — are covered in Join a shared room.

Universal Memory ​

Same API key, same memories — across all tools.

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

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

Configuration ​

VariableRequiredDefault
MNEMOVERSE_API_KEYYes—
MNEMOVERSE_API_URLNohttps://core.mnemoverse.com/api/v1

MNEMOVERSE_API_URL is the REST backend the local server talks to — it is not an MCP endpoint; never paste it into the "add MCP server by URL" field. A remote MCP connector uses https://mcp.mnemoverse.com/mcp (Remote MCP Server).

Common questions ​

How do I add persistent memory to Cursor? ​

Click the Add to Cursor button (or add the Mnemoverse MCP server to .cursor/mcp.json), restart Cursor, and the agent gets memory tools that persist across sessions. You need one free API key from console.mnemoverse.com (or use a keyless OAuth path) — the same key works in Claude Code, VS Code, and ChatGPT.

Does Cursor memory survive between sessions and projects? ​

Yes. Memories are stored in the hosted Mnemoverse API, not in the editor, so they survive restarts, new chats, and different projects — and the same memory is readable from any other connected tool.

Can Cursor share memory with Claude Code and ChatGPT? ​

Yes — that is the point. All tools connect to the same memory behind one API key or OAuth, so a rule you store in Cursor is recalled in Claude Code or ChatGPT without re-explaining.

Source & Distribution ​

npm versionMCP Registry

The MCP server is listed on the Official MCP Registry. Source code is open on GitHub under MIT.