Connect Mnem to your tools
Mnem is a standard MCP server plus opt-in capture hooks. Most tools connect in one click from the app's Connections panel; the rest take a pasted snippet and about a minute.
How connections work
One-click where supported
For Cursor, Claude Desktop, Claude Code, Zed, VS Code, and Continue.dev, the Connections panel writes the right MCP config directly — then you restart the tool once.
Manual for the rest
For Raycast, Warp, AnythingLLM, Obsidian, and others, the panel shows an exact snippet to paste. Same server, same memory.
One shared memory
Every connector talks to the same local store. Remember something in one app and recall it in another — memory_status confirms any connection end-to-end.
Connector guides
Cursor
Long-term memory for Cursor's agent — decisions and conventions recalled across every project.
Claude Desktop
Claude with a real past — recall preferences and prior work mid-conversation.
Claude Code
Memory for the terminal agent — context follows you across repos and sessions.
Zed
Memory in Zed's Agent Panel via a context server entry.
VS Code
Copilot Chat agent mode with long-term memory via MCP.
ChatGPT Desktop
Opt-in capture keeps ChatGPT conversations in your one shared memory.
Continue.dev
The open-source assistant, connected to your one shared memory.
Obsidian
Recall your long-term memory inside MCP-capable Obsidian AI plugins.
Raycast
Your memory at your fingertips — recall and remember from Raycast AI.
Warp
The agentic terminal with memory of your machines, projects, and habits.
AnythingLLM
Workspace RAG plus personal memory — agents that know your history.
Apple Shortcuts
Remember and Recall actions for Shortcuts — automate your memory.
General troubleshooting
- Most MCP clients load servers at startup — fully restart the tool after connecting.
- Test the whole path by asking one app to
remembersomething and another torecallit. - The Connections panel shows live status per app; a red state usually means the client needs a restart or the config was edited by hand.
- Auto-capture is always opt-in and separate from tool access — connecting an app never silently records it.
Tool not listed? Anything that speaks MCP can connect — use the generic snippet under Connections → Other MCP client.