Graph MIND

MCP文档知识

提供方 未标注

文档知识 stdio · 本地进程 API Key 社区 / 第三方 Claude DesktopClaudeCursorVS Code

为 AI 智能体提供本地长期记忆。逐字保留每一次对话,保存不产生任何费用,并由你的所有智能体共享。在相同测试中胜过 Mem0、MemPalace 和 agentmemory。

一句话选型结论

按资料字段整理

Graph MIND 属于文档知识类 MCP 服务器,stdio · 本地进程,API Key,可直接接入 Claude Desktop、Claude、Cursor 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

支持客户端

适用场景

记忆

安装与配置

stdio · 本地进程 API Key
客户端在本机拉起子进程,数据不出本机
  1. 1
    准备运行环境

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

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

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

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

知识库读写

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

内容整理

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

选择建议

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

值得选的地方

  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Graph MIND当前 未标注 stdio · 本地进程 本地部署 无 2026-11-20
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 · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-11-20上游最后核验时间

详细介绍

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

Turnbook

Your AI forgets everything when the session ends. This one remembers, and it never calls an LLM to do it.

No AI summaries: every conversation is kept word for word, so nothing is lost or made up on the way in, and saving costs zero model tokens. 91.8% on LongMemEval from 3.1k tokens of memory per question (details). Runs on your own PC.

Decide something with one agent on Monday. Ask another on Wednesday. It knows.

Typical memory layers (Mem0, Mastra, Supermemory, ...) Turnbook
How a conversation is saved an LLM rewrites it into facts or notes word for word
What saving costs LLM API calls for every conversation, for as long as you use it nothing
API key or cloud plan needed none
Where your conversations go to the LLM provider, and their cloud if hosted stay on your PC
What gets saved what the model or your code chooses to add every turn, automatically
Which apps share it the app you build it into Claude Code, Codex, Cursor, Copilot CLI, Gemini CLI and OpenCode, as they are
LongMemEval, gpt-5-mini answering up to 94.9% (Mastra) 91.8% from 3.1k tokens

All 500 LongMemEval_S questions, official gpt-4o judge. Rewriting every conversation with an LLM buys a few points on questions that combine sessions or dates; Turnbook keeps the original words instead and spends nothing to save them. How it compares

English · 한국어

Recorded live on one PC: Claude Code (Opus 5.5, effort high) and Codex (GPT-6.1-Sol, effort high) sharing one Turnbook memory. Model thinking time is fast-forwarded.

If Turnbook saves you tokens or repeated explanations, a ⭐ helps other people find it.

Install

Windows: download Turnbook-Setup.cmd
and double-click it, or in PowerShell:```powershell
irm https://raw.githubusercontent.com/goyohan0611-png/turnbook/main/scripts/install.ps1 | iex


macOS / Linux:```bash
curl -LsSf https://raw.githubusercontent.com/goyohan0611-png/turnbook/main/scripts/install.sh | sh

No Python needed; nothing else to set up. Restart your AI apps afterwards. Already have Python?
pip install turnbook && turnbook-install. Rather read the script and pin a version first?
Careful install.

Only Claude Code, and uv installed? It is also a plugin:```
/plugin install turnbook --marketplace goyohan0611-png/turnbook


Codex: `codex plugin marketplace add goyohan0611-png/turnbook-plugin`, then `codex plugin add turnbook@turnbook`.

Connecting an MCP client by hand

After `pip install turnbook`:```json
{
  "mcpServers": {
    "turnbook": {
      "command": "python",
      "args": ["-m", "turnbook.mcp_server"]
    }
  }
}

Claude Code: claude mcp add turnbook -- python -m turnbook.mcp_server. This gives the
tools only; turnbook-install also saves every conversation automatically.

Try it

Work as usual for a while, then open a new session, another app, or another model and ask:

  • "Where did we leave off yesterday?"
  • "Which database did we pick for the billing service, and why?"
  • "What did you change in the auth middleware last week?"
  • "What's my dog's name?" (any fact you mentioned once, in passing)

Nothing to tag or save by hand: every turn is already stored, and the agent pulls back the few
that answer the question.

What it does

  • Every agent, one memory. Claude Code, Codex, Cursor, Copilot CLI, Gemini CLI, OpenCode and
    any MCP app read and write the same memory. Decide with one, ask another; switch models, the
    memory stays.
  • The right memory in every message. In Claude Code, Codex, Copilot CLI, Gemini CLI and
    OpenCode, Turnbook looks up what your message needs from the past and adds it before the model
    answers. Nothing to ask for.
  • Free to save, on your PC. Every turn is stored word for word in one SQLite file: no model
    call, no tokens, no account, no cloud.

Everything else

  • Made for orchestration. When an orchestrator runs several agents at once, they all write
    to the same memory as they work, so what one agent decided is there for the next. Every
    memory keeps which app and session it came from.
  • Holds up as memory piles up. Grow a memory tenfold and the answer is still among the first
    30 found for 92.7% of questions (92.6% before); a search takes about 0.1 s.
    As the memory grows
  • Any language, across languages. The search model reads Korean almost as well as English:
    ask in Korean about something said in English, or the other way round. In Korean
  • Your project's documents too. turnbook docs add FOLDER keeps its Markdown and text files
    searchable beside the conversations, section by section, and up to date as they change.
  • One memory across your PCs. Run turnbook folder share, then turnbook folder on
    the other PC (the AI tells you the command; it never moves your memory by itself, so a web page
    cannot either). Office network or Tailscale, over TLS, every line
    encrypted before it leaves a PC.
  • Hand a memory to someone else as a file. turnbook export FILE writes all of it;
    --project FOLDER writes only the conversations held in that folder. They run
    turnbook import FILE.
  • Yours. No account, no cloud of its own, no telemetry. Secrets are masked before anything is
    stored, and "delete the password I typed earlier" deletes it everywhere. docs/privacy.md
  • Teams, if you want them. Share a project's decisions and progress with teammates' AIs, never
    your personal memory; files stay in Slack and GitHub. docs/teams.md

Works with

The installer finds these and connects them; run it again after installing a new one.

app conversations saved how
Claude Code every turn reads its transcripts; a hook adds relevant memory to each message
Codex CLI every turn reads its transcripts; a hook adds relevant memory to each message (trust it once in /hooks)
Cursor every turn reads its transcripts
Copilot CLI every turn reads its transcripts; a hook adds relevant memory to each message
Claude Desktop (Cowork) every turn reads its session files
Gemini CLI every turn hooks; also adds relevant memory before each answer
OpenCode every turn plugin; also adds relevant memory before each answer, for any model
Claude Desktop chat, Windsurf, VS Code Copilot, Cline, LM Studio what the model saves MCP tools

Any other MCP client works through the tools: see the hand-written config above.

How it works```mermaid

flowchart LR
A["Claude Code · Codex · Cursor<br/>Gemini CLI · OpenCode · ..."] -- "transcripts, hooks, plugin" --> C["capture service<br/>(runs in the background)"]
C -- "verbatim turns,<br/>secrets masked" --> S[("your memory<br/>on this PC")]
S --> I["local search<br/>words + meaning + time"]
A -- "a question that needs the past" --> I
I -- "the few turns that answer it<br/>(a few thousand tokens)" --> A
```

  • Saving costs nothing. Turns are stored as they were said. No model summarises or extracts
    anything at write time, so nothing is lost or invented on the way in, and no tokens are spent.
  • Search runs on your PC. Word search, a local embedding model (Google's EmbeddingGemma,
    4-bit; ONNX, no GPU) and when things were said are combined, then ordered by a small learned
    score; the agent gets a short packet with the source turns, not a dump of history.
  • The model you already use does the thinking. Turnbook hands it evidence; it answers.
    When models get better, the answers get better without changing the memory.

Beyond agent memory

Underneath, Turnbook is RAG over chat history with everything before the answer built in. A
typical RAG stack is assembled from parts; Turnbook runs every step up to the answer on its own
and leaves only the answer to the model you already use:

Step Typical RAG stack Turnbook
Collect an ingestion script you write every turn saved automatically from your agents
Chunk splitting rules to tune one turn per entry, word for word
Embed an embedding API, paid per token a local model, free
Store a vector database to run one SQLite file
Retrieve search code to write words, meaning and time, re-ranked by a small learned score
Hand over prompt-assembly code a bounded evidence packet over MCP
Answer your LLM your LLM (Claude, Codex, ...)

The same engine could serve a chatbot that remembers each of its users, a support bot that
recalls past tickets, or a team's searchable decision log. Today it ships as a personal, local
memory; a Python API and multi-user server mode are not built yet. Interested? Open an issue.

Does it work?

LongMemEval is the public benchmark for long-term
chat memory: 500 questions over about 50 past sessions each. Turnbook's scores use gpt-5-mini as
the answer model with the benchmark's own prompt and official gpt-4o judge; a question left
unanswered counts as wrong.

text the answer model reads (median) accuracy model tokens spent saving memory
3.1k tokens (the default) 91.8% (459/500) 0
25k tokens 93.0% (465/500) 0

How it compares

Other memories publish their own LongMemEval scores, each with its own answer model, judge and
setup, so they are not one ranking. The closest to like-for-like:
Mastra's Observational Memory reports 94.9%
with the same answer model, gpt-5-mini, which reads about 30k tokens of observations that
gemini-2.5-flash wrote while the conversations were saved. It and others (Mem0, Supermemory) run
an LLM over every conversation when saving it, writing dated facts and replacing outdated ones; that is
where Turnbook loses points: 33 of its 41 misses are questions that combine several sessions,
reason about dates, or need the newest value of something that changed. Turnbook keeps the
original words, spends no model tokens saving them, and runs on your own PC.

What makes the difference

The learned re-ranker. Without it (plain rank fusion, no weight fitted on any benchmark):
87.0% of all 500, and 86.8% of the 380 questions never used for tuning, where the shipped search
scores 91.1%. It helps most where answers are spread over several sessions.
norerank

The memory added to each message (4 items, ~300 tokens) is a hint, not the full search: alone
it answers 61.4% of the same 500; brain_context, which the model calls for more, answers 91.8%.
It does not get in the way of unrelated work: on 200 GSM8K math problems with an unrelated
person's memory attached, gpt-5-mini solved 191, against 193 without it (p = 0.69).
hook ·
interference

As the memory grows

More past conversations means more that looks like the one you mean. On LoCoMo (1,536 questions),
with each person's memory grown tenfold by storing other people's conversations beside it, the
answer turn stays among the first 30 found for 92.7% of questions (92.6% before it grew);
Turnbook with its re-ranker turned off drops from 90.2% to 88.4%. A search takes 30 ms at 5,882 turns and 116 ms at 55,882.
Larger memories are being measured.
scale

In Korean

Four LoCoMo conversations translated into Korean (582 questions). Search by meaning alone, share
of questions whose answer turn is among the first 30 found: English 90.2%, Korean 86.9%, a Korean
question about an English memory 87.8%. Word search finds "콩이" in "콩이를" (Korean particles).
research/runs/graph-v9.21-korean

Every question, answer and verdict is in research/runs/; method, failures and
how to rerun it: docs/benchmarks.md.

FAQ

Will it slow my PC down? The background service uses about 2% of one CPU core when nothing new
is coming in. An app's memory server holds about 525 MB. A memory search takes about 40 ms
(46 ms at the 95th percentile on a GitHub runner);
the first one after an app starts, about 1.4 s. Each new turn takes about 0.1 s to embed; the
service runs below normal CPU priority and embeds backlogs at half pace. On a first install, the
conversations already on the PC are read in the background while word search answers at once.

Which search model? EmbeddingGemma
(about 200 MB, downloaded from Hugging Face on first use). A memory from an older version is
read again with it in the background and moves over by itself. turnbook model shows which
model is in use; turnbook model REPO@FILE switches to any ONNX embedding model on Hugging Face (memory is read again with it in
the background). A model you picked is never deleted.
EmbeddingGemma is provided under the
Gemma Terms of Use; it is not part of Turnbook's own code
or license.

What does it cost? Nothing. No API key and no model calls of its own; your AI app reads a
packet of a few thousand tokens when a question needs the past.

Does anything leave my PC? No, unless you share the memory with your own other PCs or a team.
No telemetry. Secrets (API keys, passwords, card numbers...) are masked before storing.

How is this different from CLAUDE.md or an app's built-in memory? Those keep notes a model
wrote, one app at a time. Turnbook keeps every turn as it was said and shares it across every
app and model on the PC.

Korean? Yes: Korean and English conversations, and questions in either language. With the
default model, search by meaning trails English by about 3 points in Korean, and a Korean
question finds an English memory about as often: In Korean.

How do I remove it? turnbook-uninstall disconnects every app and stops the service; the
memory stays in ~/.turnbook unless you add --purge.

> [!NOTE]
> Used daily on Windows. macOS and Linux pass every test in CI on every change, including an
> upgrade from the previous release, but have seen less daily use: issues are welcome.

More

MCP tools · See your memory in 3D
(turnbook-view) · Agent continuity prototype · Changelog · Security ·
Development: pip install -r requirements.txt, then python -m unittest discover -s tests

Contributions are welcome. License: Apache-2.0.

常见问题

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

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Graph MIND 怎么在 Claude Desktop、Claude、Cursor 里配置?

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

Graph MIND 收费吗?

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

Graph MIND 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

Graph MIND 支持哪些客户端?

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

Graph MIND 能提供哪些能力?

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

Graph MIND 需要什么运行环境?

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

Graph MIND 是本地还是远程?

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

热门专题

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

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