Does Memory (reference) work with Cursor?

Result

Steps

1. install OK
2. connected OK
3. tools visible OK
4. agent task: recall across sessions OKstore in session 1, recall in a fresh session 2 (the token only appears in session 1's prompt)

From our own harness run, not the maker’s claims. How we test.

What happened in this run

Install config we used

{
 "mcpServers": {
  "ref-memory": {
   "command": "npx",
   "args": [
    "-y",
    "@modelcontextprotocol/server-memory"
   ],
   "env": {
    "MEMORY_FILE_PATH": "/workspace/timmy/harness/sandbox/memory.jsonl"
   }
  }
 }
}

Connection check

ref-memory: ready

Tools the app saw

9 tools in the app (protocol check found 9).

Agent task: recall across sessions

• Tool calls, in order: ref-memory:search_nodes, ref-memory:open_nodes

Raw details from our harness log for this run. Secrets redacted.

Set it up in Cursor

Copy-paste config for every app is on the Memory (reference) page. Not connecting? Cursor MCP troubleshooting.

Other apps we tested it in: Claude Code (passed) · Claude Desktop (passed) · ChatGPT (Codex) (passed).

All MCP servers tested in Cursor