MAGNEMO

Name: MAGNEMO
Author: magnemo-ai

作者：magnemo-ai版本 0.6.11i★ –i在你的电脑上运行

注册名称ai.magnemo/magnemo

安装

概览

作者提供的说明（英文原文）

Persistent Memory for AI Agents, in plain local files. No network calls of its own.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 搜索与 AI 记忆
你需要填写：MAGNEMO_VAULT

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： MAGNEMO_VAULT, MAGNEMO_AGENT

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "magnemo": {
      "command": "uvx",
      "args": [
        "magnemo-mcp"
      ],
      "env": {
        "MAGNEMO_VAULT": "your-value",
        "MAGNEMO_AGENT": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add magnemo --env MAGNEMO_VAULT=your-value --env MAGNEMO_AGENT=your-value -- uvx magnemo-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "magnemo": {
      "command": "uvx",
      "args": [
        "magnemo-mcp"
      ],
      "env": {
        "MAGNEMO_VAULT": "your-value",
        "MAGNEMO_AGENT": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "magnemo": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "magnemo-mcp"
      ],
      "env": {
        "MAGNEMO_VAULT": "your-value",
        "MAGNEMO_AGENT": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

MAGNEMO_VAULT 必填 env
Absolute path to the vault folder (create one with: magnemo init ./vault). Plain markdown files you own.
MAGNEMO_AGENT env
The name this agent signs its entries with. Default: agent.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过域名 magnemo.ai 验证（注册中心会核实域名所有权）
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“搜索与 AI 记忆”中的其他服务器比较i

星标数多于此分类中其他 7234 个服务器的 0%
发布到注册中心的时间比此分类中其他 7234 个服务器的 81% 更新
基础检查结果等于或优于此分类中其他 7234 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

MAGNEMO 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：MAGNEMO_VAULT

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.6.11）于8天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Context7, Codebase Memory, Exa

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Context7

作者：upstash

Up-to-date docs for AI agents

电脑或云端★ 64,224MIT3天前更新

安装

Codebase Memory

作者：DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

在你的电脑上运行★ 48,148MIT20天前更新

安装

Exa

作者：exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

在云端运行★ 5,213MIT44天前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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.

Your agent writes one line down and keeps working. Say keep, and it is Memory.

Site · Manual · Changelog · X @Magnemo_AI · Known limits

Install in one paste

In three lines:

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, and the first line in CLAUDE.md

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, and a short block in CLAUDE.md that tells every new session where this project's Memory is. In Cursor, Windsurf or another client, use the block for your client under "Install in your client".)

Set up MAGNEMO in this project:

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
Initialize the vault: magnemo init
Register the MCP server: run magnemo mount — it adds MAGNEMO to this project's MCP config and keeps any servers already there.
Verify: run magnemo doctor and confirm everything passes.
Then ask me to restart you, so MAGNEMO's tools load, and to say this when you are back: "Look around this folder, tell me what this project is for, and stage that as the first note." Your agent never waits on you. When you want something kept, say keep.

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: Look around this folder, tell me what this project is for, and stage that as the first note. Your agent writes one line down and keeps working. Say keep, and it is Memory. 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 26–28, 2026, Claude Code 2.1.309. Seven tools; the yes in the chat; `pending` reads a body.	`magnemo mount`, or `claude mcp add magnemo -e MAGNEMO_VAULT=/absolute/path/to/vault -- uvx magnemo-mcp`
Claude Desktop	untested end to end	the `uvx` block under "Install in your client", with absolute paths
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.

Their pages: Mem0 overview, platform and open source, add, history, quickstart, delete, export · Zep concepts, facts, security, deleting data, Graphiti · Letta MemFS, memory settings, local mode · Basic Memory README, what it is, tools, note format, semantic search, suggestions, file history. A cell that is wrong or out of date: open an issue and it is fixed.

Listed on the official MCP registry (ai.magnemo/magnemo) · PyPI · mcpservers.org · Glama · awesome-mcp-servers. Tested on every push, on Python 3.9, 3.11 and 3.12: 370 tests, as of Oct 28, 2026 (the runs).

What's new

0.6.11 · Oct 28, 2026 · magnemo mount writes the first line in CLAUDE.md, so every new session knows where this project's Memory is. pending reads a note nobody has kept yet.
0.6.10 · Oct 26, 2026 · Your agent never stops to ask. Say keep in the chat, and the record says how the yes was given.
0.6.9 · Oct 22, 2026 · A seat's report files itself as a receipt and asks nothing; a yes is for Memory. Sentinel reads a seat's quote as a quote.

Every release: CHANGELOG.md.

For builders. MAGNEMO is an MCP server with four verbs — retrieve, stage, bootpack, handoff — plus keep, drop, pending, 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](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 seven tools and calls them; a yes in the chat keeps a note, and pending reads a body (last run Oct 28, 2026: Claude Code 2.1.309, the 0.6.11 server).

claude mcp add magnemo -e MAGNEMO_VAULT=/absolute/path/to/vault -- uvx magnemo-mcp

(`claude mcp lis

只显示了开头部分；其余内容请在仓库中阅读