Does Memory (reference) work with Claude Desktop?
Yes. Memory (reference) passed every step of our test in Claude Desktop on Oct 14, 2026: it installed, connected, its tools were visible, and an agent used it to finish a real task.
Result
ResultPassed
Date testedOct 14, 2026
Plan tested onNot recorded for this run
App versionClaude Desktop 2.37337.1 (Linux beta)
Steps
- install OK
- connected OK
- tools visible OK
- agent task: recall across sessions OKstore in session 1, recall in a fresh session 2 (the token only appears in session 1's prompt)
Test note: server wrapped in harness/scripts/mcp_tee.py to record JSON-RPC; prompts typed via xdotool; tool Allow pop-ups approved by the operator for test servers only; model = app default
From our own harness run, not the maker’s claims. How we test.
What happened in this run
Install config we used
{
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}Connection check
initialize seen in tee log after app restartTools check
tools/list answered (tee log)
Agent task: recall across sessions
- 1 calls reached the server
- Agent’s answer (excerpt):
The memory store has more than one toolpassed test code saved, and they don't agree: TP-F42B55 (reference); TP-220F1B and TP-F2D3E1 (credential). [older codes a…
Raw details from our harness log for this run. Secrets redacted.
Set it up in Claude Desktop
Copy-paste config for every app is on the Memory (reference) page. Not connecting? Claude Desktop MCP troubleshooting.
Other apps we tested it in: Claude Code (passed) · Cursor (passed) · ChatGPT (Codex) (passed).