Magnemo-AI/magnemo

**Governed Memory for AI Agents. Sessions die. The Memory doesn't.**
Magnemo is a 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.
Site · Manual · Changelog · Known limits
Install in one paste
In three lines:
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".)
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.8.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". Listed on the official MCP registry (ai.magnemo/magnemo), PyPI, Glama, mcpservers.org and awesome-mcp-servers.
**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.