Magnemo

MCP文档知识

提供方 未标注

文档知识 stdio · 本地进程 未标注 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

本地、零依赖的AI代理记忆MCP:代理暂存,人工提升,每条记录都有凭证。

一句话选型结论

按资料字段整理

Magnemo 属于文档知识类 MCP 服务器,stdio · 本地进程,鉴权方式未标注,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式stdio · 本地进程 鉴权未标注 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

记忆

安装与配置

stdio · 本地进程 未标注
客户端在本机拉起子进程,数据不出本机
uvx magnemo-mcp

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Magnemo当前 未标注 stdio · 本地进程 本地部署 有 未标注
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类文档知识本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

16.2 KB
来自项目仓库与上游目录的原文,未做删改

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:```bash
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".)```text
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: "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 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).```bash
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//claude.app/Contents/MacOS/claude`; run that in place of `claude`.

**Claude Desktop** — untested end to end here. The server this block starts was run the way Claude Desktop starts it
(Oct 28, 2026, the 0.6.11 server). Claude Desktop → Settings → Developer → Edit Config, then
`claude_desktop_config.json`. Claude Desktop does not read your shell's PATH, so both paths are absolute: `which uvx`
prints the first.```json
{
  "mcpServers": {
    "magnemo": {
      "command": "/absolute/path/to/uvx",
      "args": ["magnemo-mcp"],
      "env": { "MAGNEMO_VAULT": "/absolute/path/to/vault", "MAGNEMO_AGENT": "claude-desktop" }
    }
  }
}

Restart Claude Desktop after saving.

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):```json
{
"mcpServers": {
"magnemo": {
"command": "uvx",
"args": ["magnemo-mcp"],
"env": { "MAGNEMO_VAULT": "/absolute/path/to/vault" }
}
}
}


**VS Code / Copilot** — untested here; per VS Code's docs.

Or `.vscode/mcp.json` in the workspace:```json
{
  "servers": {
    "magnemo": {
      "type": "stdio",
      "command": "uvx",
      "args": ["magnemo-mcp"],
      "env": { "MAGNEMO_VAULT": "/absolute/path/to/vault" }
    }
  }
}

Windsurf — untested; ~/.codeium/windsurf/mcp_config.json:```json
{
"mcpServers": {
"magnemo": {
"command": "uvx",
"args": ["magnemo-mcp"],
"env": { "MAGNEMO_VAULT": "/absolute/path/to/vault" }
}
}
}


**Cline** — untested; Cline → MCP Servers → Configure → `cline_mcp_settings.json`:```json
{
  "mcpServers": {
    "magnemo": {
      "command": "uvx",
      "args": ["magnemo-mcp"],
      "env": { "MAGNEMO_VAULT": "/absolute/path/to/vault" },
      "disabled": false
    }
  }
}

Continue — untested; ~/.continue/config.yaml (or a file in .continue/mcpServers/):```yaml
mcpServers:
- name: magnemo
command: uvx
args: ["magnemo-mcp"]
env:
MAGNEMO_VAULT: /absolute/path/to/vault


**Gemini CLI** — untested; `~/.gemini/settings.json`:```json
{
  "mcpServers": {
    "magnemo": {
      "command": "uvx",
      "args": ["magnemo-mcp"],
      "env": { "MAGNEMO_VAULT": "/absolute/path/to/vault" }
    }
  }
}

Codex CLI — untested; ~/.codex/config.toml:```toml
[mcp_servers.magnemo]
command = "uvx"
args = ["magnemo-mcp"]
env = { MAGNEMO_VAULT = "/absolute/path/to/vault" }


**Zed** — untested; `settings.json` → `context_servers`:```json
{
  "context_servers": {
    "magnemo": {
      "source": "custom",
      "command": "uvx",
      "args": ["magnemo-mcp"],
      "env": { "MAGNEMO_VAULT": "/absolute/path/to/vault" }
    }
  }
}

After the install, the loop is the same everywhere: your agent writes to staging, you review.```bash
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&#x27;s yes from an agent&#x27;s; a yes in the chat counts, and the record says how it was given.**

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 and cannot keep a note on its own authority; it carries your yes, and the record says so.
Say yes in the chat and `keep` carries it, ledgered unverified; a click your client draws or a yes at your terminal is a verified one. 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 · `keep` / `drop` carry your yes or no · `pending` lists what waits |
| 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&#x27;s partition
  ops/      knowledge/ playbooks/ clients/ decisions/ style/  ← example: an ops team&#x27;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.

Tests```bash

python -m unittest discover -s tests -v # incl. full MCP round-trips (legacy + four-verb)

or: pip install -e ".[test]" && pytest

```
The same suite runs on every push, on Python 3.9, 3.11 and 3.12: the runs.

Everything that shipped

Release by release, with the design notes that used to live here: CHANGELOG.md.

— Silver Valley Technologies Inc. · Phase 1 of 3 · The memory that learns is
the memory that is governed.


mcp-name: ai.magnemo/magnemo · Source · Security · Privacy

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
Magnemo 怎么安装?

在客户端按下面的安装命令接入:uvx magnemo-mcp。装完在客户端配置里引用同一个包或端点。

Magnemo 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Magnemo 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Magnemo 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

Magnemo 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Windsurf、Cline;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Magnemo 能提供哪些能力?

资料显示能力标签包括 记忆。具体工具清单以官方文档为准。

Magnemo 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

Magnemo 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。