Puter MCP
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
作者提供的说明(英文原文)
Persistent Memory for AI Agents, in plain local files. No network calls of its own.
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
需要 MAGNEMO 的密钥(在开发者网站注册,可能收费) · 需要先在电脑上安装 Python (uv)(只需一次) · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
SettingsDeveloperEdit Config
{
"mcpServers": {
"magnemo": {
"command": "uvx",
"args": [
"magnemo-mcp"
],
"env": {
"MAGNEMO_VAULT": "your-value",
"MAGNEMO_AGENT": "your-value"
}
}
}
}只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 MAGNEMO 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 MAGNEMO,或回答中出现 MAGNEMO 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 MAGNEMO
MAGNEMO 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
A · 使用能连接 MAGNEMO 的应用
可连接 Claude Code,但需要先准备
需要 MAGNEMO 的密钥(在开发者网站注册,可能收费) · 需要先在电脑上安装 Python (uv)(只需一次)
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add magnemo --env MAGNEMO_VAULT=your-value --env MAGNEMO_AGENT=your-value -- uvx magnemo-mcp按 Enter 前,把“your-value”改成你的密钥
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
应能看到 MAGNEMO 在列表中并显示已连接
用 MAGNEMO 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 MAGNEMO,或回答中出现 MAGNEMO 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor,但需要先准备
需要 MAGNEMO 的密钥(在开发者网站注册,可能收费) · 需要先在电脑上安装 Python (uv)(只需一次)
在 MAGNEMO 的设置中,MAGNEMO_VAULT, MAGNEMO_AGENT 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 MAGNEMO 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 MAGNEMO,或回答中出现 MAGNEMO 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code,但需要先准备
需要 MAGNEMO 的密钥(在开发者网站注册,可能收费) · 需要先在电脑上安装 Python (uv)(只需一次)
在 MAGNEMO 的设置中,MAGNEMO_VAULT, MAGNEMO_AGENT 还是空的,填入你的密钥并保存
只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人
用 MAGNEMO 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 MAGNEMO,或回答中出现 MAGNEMO 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
Claude Code
claude mcp add magnemo --env MAGNEMO_VAULT=your-value --env MAGNEMO_AGENT=your-value -- uvx magnemo-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"magnemo": {
"command": "uvx",
"args": [
"magnemo-mcp"
],
"env": {
"MAGNEMO_VAULT": "your-value",
"MAGNEMO_AGENT": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"magnemo": {
"command": "uvx",
"args": [
"magnemo-mcp"
],
"env": {
"MAGNEMO_VAULT": "your-value",
"MAGNEMO_AGENT": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"magnemo": {
"type": "stdio",
"command": "uvx",
"args": [
"magnemo-mcp"
],
"env": {
"MAGNEMO_VAULT": "your-value",
"MAGNEMO_AGENT": "your-value"
}
}
}
}MAGNEMO_VAULT 必填 envMAGNEMO_AGENT env这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月11日
注册名称已通过域名 magnemo.ai 验证(注册中心会核实域名所有权)
代码最后更新于前天
使用 Apache-2.0
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:MAGNEMO_VAULT
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于前天,最新版本(0.6.11)于13天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。
同一分类中有:Puter MCP, XcodeBuildMCP, XcodeBuildMCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
按原文从作者的仓库复制。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
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:
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.
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".
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).
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.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.
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