The Memory MCP. Your AI remembers. You keep what matters.
Magnemo is Memory for your AI, kept on your computer in plain files. Your AI writes down what it learns as it works; nothing becomes Memory until you approve it, and every Memory shows who wrote it and who approved it.
When your agent writes something down, Magnemo asks you in the chat. One click.
Persistent Memory for AI Agents. Nothing becomes Memory until you approve it. Plain local files, a receipt on every entry.
pip install magnemo # Python 3.11 or newer
magnemo init # makes the vault: a folder of plain files
magnemo mount # writes .mcp.json, the file Claude Code reads
Or let your agent do it. Open Claude Code in any of your project folders, and paste this. (Its magnemo mount step writes .mcp.json, the file Claude Code reads. In Cursor, Windsurf or another client, use the block for your client under "Install in your client".)
Set up Magnemo in this project:
1. Install it: pip install magnemo. It needs Python 3.11 or newer. If pip can't find it, install uv (curl -LsSf https://astral.sh/uv/install.sh | sh) and then run: uv tool install magnemo
2. Initialize the vault: magnemo init
3. Register the MCP server: run magnemo mount — it adds Magnemo to this project's MCP config and keeps any servers already there.
4. Verify: run magnemo doctor and confirm everything passes.
5. Then ask me to restart you, so Magnemo's tools load, and to say this when you are back: "Use Magnemo to remember what this project is."
If anything fails, show me what went wrong and fix it if you can.
Plant the seed: one paste, and your agent grows a Memory.
After the restart, say it: Use Magnemo to remember what this project is. Your agent writes one line down, and
Magnemo asks you in the chat to approve it. One click. Then ask what it remembers.
Works with
One server, the same in every client. Tested where it says so; the rest follow each client's own docs.
Client
Tested
How
Claude Code
yes: Oct 12, 2026, Claude Code 2.1.296. The four tools, and the question in the chat: one click approved a note.
magnemo mount, or claude mcp add magnemo -e MAGNEMO_VAULT=/absolute/path/to/vault -- uvx magnemo-mcp
Claude Desktop
untested
open magnemo-0.6.9.mcpb from the latest release
Cursor
untested
the Add to Cursor link below, or .cursor/mcp.json
VS Code
untested
.vscode/mcp.json
Windsurf
untested
~/.codeium/windsurf/mcp_config.json
Cline
untested
cline_mcp_settings.json
Continue
untested
~/.continue/config.yaml
Gemini CLI
untested
~/.gemini/settings.json
Codex CLI
untested
~/.codex/config.toml
Zed
untested
settings.json → context_servers
Each client's exact block is under "Install in your client".
How it compares
Five questions, answered from each project's own docs (read Oct 12, 2026, checked again Oct 22; the pages are linked under the table).
Magnemo
Mem0
Zep
Letta
Basic Memory
Where the memory lives
Plain markdown files in a folder on your computer
A hosted platform run by Mem0; open source: a local Qdrant store and a SQLite history file
Zep: a managed cloud service, or in your own VPC. Graphiti, its open-source engine: a graph database you run
Markdown files in a git repository that belongs to the agent: hosted by Letta, or on your device in local mode
Markdown files on your disk with a local SQLite index; an optional cloud
Who approves a write
You. An agent's write waits in staging until your yes
An LLM extracts facts from the messages and stores them; their docs describe no approval step
Messages are ingested into the graph as they arrive; their docs describe no approval step
The agent updates its own memory; the background review "does not ask you for approval"
The assistant writes notes directly; the cloud has suggested edits that can be accepted or rejected
Author and approver on every entry
Both, in each file's header (author, reviewed_by) and in an append-only ledger
User, agent, app and run ids, timestamps, and a change history per memory; their docs name no approver field
When a fact was true and when it stopped, traced to its source episode; their docs name no approver field
Every memory edit is a git commit; their docs do not say what the commit records
Title, type, tags and dates; author is a field you may add; their docs name no approver field
Network calls of its own
None. No model call and no embedding call; git push to a backup, if you add one
OpenAI by default for the model and the embeddings; other providers are listed, Ollama among them
Zep is a cloud API. Graphiti defaults to OpenAI; local model servers are documented
Local mode keeps state on your device; inference goes to the provider you choose, which can be a local one
Runs locally; the default embeddings run on your machine with no API key
What you can take back
A no is kept with its reason; a replaced note is archived with a forward link; nothing deletes; the files are yours to edit
Delete, update, and a history per memory; export is on the hosted platform
Delete nodes, edges and episodes; a replaced fact is invalidated, not deleted
The git history of every memory edit; the files can be read and edited
Plain files you edit and can track with git; a delete tool; the cloud keeps every saved version
Where each of them is ahead. Mem0 extracts memories for you, searches them by meaning, and has Python and JavaScript SDKs, a REST API and a hosted platform. Zep keeps a knowledge graph that knows when each fact was true, as a managed service with SDKs in three languages. Letta is a whole agent platform, with an SDK, a CLI and background agents that tend the memory. Basic Memory searches by keyword and by meaning with embeddings that run on your machine, links notes into a graph, and syncs through its cloud. Magnemo has none of that: its search is keyword search (KNOWN_LIMITS.md), there is no graph and no hosted service. What it has is the approval and the record.
For builders. Magnemo is an MCP server with four tools — retrieve, stage,
bootpack, handoff — and a CLI for your side: review, promote, reject.
It runs on your machine, in plain markdown files you own. The package imports no network
module (magnemo doctor scans for one on every run); the only traffic is git push to a
backup destination, if you add one. Every promotion is recorded with who wrote the entry,
the name given for the yes, when, and through which gate. Trust is computed from that
record, never asserted. It mounts beside any memory you already
run (a folder of notes, Obsidian, a RAG stack). Python 3.11+, zero dependencies,
Apache-2.0.
Fresh vault? THE CHARTER section will say it isn't promoted yet — that is the
governance speaking: Magnemo never fabricates canon. Stage a charter, review it,
promote it, and every boot thereafter serves it back verbatim.
(magnemo not found after install? pip's script folder isn't on PATH —
python3 -m magnemo always works.)
Open beta — read KNOWN_LIMITS.md before trusting it with anything you can't lose. Honest caveats, no fine print.
Install in your client
One server, said ten ways. Every block below is the same thing: uvx magnemo-mcp with MAGNEMO_VAULT pointing at
the folder your Memory lives in (make one with magnemo init ./vault). Tested on this Mac where it says so;
the rest is from each client's own docs and marked untested — corrections welcome, open an issue.
Claude Code — tested: a Claude Code session mounts the server, lists the four tools and calls them, and draws
the question in the chat (last run Oct 12, 2026: Claude Code 2.1.296, the 0.6.8 server).
claude mcp add magnemo -e MAGNEMO_VAULT=/absolute/path/to/vault -- uvx magnemo-mcp
(claude mcp list shows magnemo … ✔ Connected. Add -s project to write it into the repo's .mcp.json for your team.)
Only have the desktop app? claude may not be a command in your shell. On a Mac the app keeps its own copy at
~/Library/Application Support/Claude/claude-code/<version>/claude.app/Contents/MacOS/claude; run that in place of claude.
Claude Desktop — untested end to end here. Download the extension from the latest release —
magnemo-0.6.9.mcpb — and open it; Claude Desktop asks for the
vault folder and does the rest. (The connectors directory listing follows once it is accepted.)
Cursor — untested here (not installed on this Mac); the link and the block follow Cursor's docs.
Or ~/.cursor/mcp.json (or .cursor/mcp.json in the project):
After the install, the loop is the same everywhere: your agent writes to staging, you review.
magnemo yes # promote the top of the queue (yes <id-fragment> · yes --all)
magnemo no <id> --reason "…" # reject one — the reason is required; rejections teach
magnemo review # the interactive queue, when you want to read first
magnemo doctor # python, vault, config, ledger, and the mount — scans the package for network modules too
Anything that speaks MCP over stdio mounts the same way. The remote door (ChatGPT and hosted clients) is on its way in 0.7.0.
How it works
The yes is checked: nothing becomes Memory without a yes, and the engine can tell a person's yes from an agent's.
Magnemo is Memory with a constitution: every fact carries provenance, every agent write waits in your review queue
before it becomes Memory, and every decision lands in a Trust Ledger.
Your agent gets four verbs. Approving is not one of them.
The yes is yours: Magnemo asks you in the chat, and your answer never passes through the agent. KNOWN_LIMITS.md says what that does and does not stop; docs/MCP.md has the clients it works in.
Actor
Door
Can do
Agents
MCP server (stdio)
retrieve canonical memory · stage → staging only, the one write tool · bootpack on wake · handoff at the boundary
You
CLI + git (any editor)
review the queue · promote / reject · edit anything · own everything
Zero dependencies. Pure Python standard library, 3.11 or newer. Nothing else to install, nothing to trust but this code.
The vault
vault/
dev/ knowledge/ playbooks/ decisions/ debt/ ← example: a dev team's partition
ops/ knowledge/ playbooks/ clients/ decisions/ style/ ← example: an ops team's partition
shared/ tickets/ changelog/ ← interop bus (gated)
_staging/ agent writes await review here
_index/ machine-managed
_ledger/ trust_ledger.jsonl — append-only, never forgets
Every note is markdown with provenance frontmatter (author, written, source,
status, reviewed_by, supersedes, strength). Provenance is the file format.
Privacy
Your Memory lives on your computer, in plain files you can open. No network calls of its own. Add a backup remote and it pushes there, nowhere else.
The precise version: the package imports no network module, and magnemo doctor scans for one every time it runs. If you add a backup destination, the engine runs git push to it. The full page: https://magnemo.ai/privacy
Guarantees (Phase 1 — Governed Recall)
Through the MCP server, agent writes NEVER reach canonical stores directly — staging only, always.
Search returns canonical (promoted) notes only. Staged notes are not searched. The boot pack shows staged material marked as staged: the titles of open threads and of the top staged notes, and the last handoff's cut line with a pointer to its note.
Partition walls enforced per agent (MAGNEMO_PARTITIONS); cross-partition = DENIED.
Supersession is explicit: old notes archive with a forward link. Nothing deletes.
Rejections are kept and recorded — rejections teach.
Every promote/reject lands in the append-only Trust Ledger with actor + reason.
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Perguntas
Como instalo MAGNEMO?
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
MAGNEMO precisa de uma chave de API?
O publicador lista estas variáveis de ambiente: MAGNEMO_VAULT, MAGNEMO_AGENT.
Qual transporte MAGNEMO usa?
MAGNEMO roda localmente via stdio.
Quando MAGNEMO foi verificado pela última vez?
Última verificação: 2026-11-09. Persistent Memory for AI Agents. Nothing becomes Memory until you approve it. Plain local files, a receipt on every entry.