Turbo Quant Memory

Name: Turbo Quant Memory
Author: Lexus2016

作者：Lexus2016版本 0.34.0i★ –i在你的电脑上运行

注册名称io.github.Lexus2016/turbo-quant-memory

安装

概览

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

Local-first memory and knowledge graph for coding agents. Compact retrieval, no network.

PopNx MCP 的三大支柱

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

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

它能帮你做什么

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

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

安装

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

安装之前

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

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

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

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

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

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

{
  "mcpServers": {
    "turbo-quant-memory": {
      "command": "uvx",
      "args": [
        "turbo-quant-memory",
        "serve"
      ],
      "env": {
        "TQMEMORY_FTS_LANGUAGE": "your-value",
        "TQMEMORY_EMBEDDING_BACKEND": "your-value",
        "TQMEMORY_MIGRATE_ON_STARTUP": "your-value",
        "TQMEMORY_SECRETS_PASSPHRASE": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add turbo-quant-memory --env TQMEMORY_FTS_LANGUAGE=your-value --env TQMEMORY_EMBEDDING_BACKEND=your-value --env TQMEMORY_MIGRATE_ON_STARTUP=your-value --env TQMEMORY_SECRETS_PASSPHRASE=your-value -- uvx turbo-quant-memory serve

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

在 Cursor 中打开

或者自己复制设置

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

{
  "mcpServers": {
    "turbo-quant-memory": {
      "command": "uvx",
      "args": [
        "turbo-quant-memory",
        "serve"
      ],
      "env": {
        "TQMEMORY_FTS_LANGUAGE": "your-value",
        "TQMEMORY_EMBEDDING_BACKEND": "your-value",
        "TQMEMORY_MIGRATE_ON_STARTUP": "your-value",
        "TQMEMORY_SECRETS_PASSPHRASE": "your-value"
      }
    }
  }
}

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

在 VS Code 中打开

或者自己复制设置

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

{
  "servers": {
    "turbo-quant-memory": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "turbo-quant-memory",
        "serve"
      ],
      "env": {
        "TQMEMORY_FTS_LANGUAGE": "your-value",
        "TQMEMORY_EMBEDDING_BACKEND": "your-value",
        "TQMEMORY_MIGRATE_ON_STARTUP": "your-value",
        "TQMEMORY_SECRETS_PASSPHRASE": "your-value"
      }
    }
  }
}

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

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

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

需要你填写的值

TQMEMORY_FTS_LANGUAGE env
Snowball stemmer for the BM25 lane. Use Russian for Cyrillic-dominant corpora.
TQMEMORY_EMBEDDING_BACKEND env
Embedder backend. Default fastembed (ONNX); sentence-transformers needs the [torch] extra.
TQMEMORY_MIGRATE_ON_STARTUP env
Set to 1 to apply pending schema migrations automatically on startup.
TQMEMORY_SECRETS_PASSPHRASE 机密 env
Argon2id passphrase for the secrets vault on headless hosts. Omit to use the OS keyring.

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

它能做什么

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

基础检查i

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

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

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

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

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

常见问题

Turbo Quant Memory 安全吗？

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

它需要哪些密钥或代码？

你需要填写：TQMEMORY_SECRETS_PASSPHRASE

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

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

它还在维护吗？

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

哪些应用可以使用它？

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

有什么可以替代它？

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

替代选择

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

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

Context7

Up-to-date docs for AI agents

作者：upstash广泛使用↓ 97.3万/周★ 6.4万3天前更新

电脑或云端

安装

Codebase Memory

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

作者：DeusData广泛使用↓ 1.8万/周★ 4.8万23天前更新

在你的电脑上运行

安装

Exa

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

作者：exa-labs广泛使用★ 52132个月前更新

在云端运行✓ exa.ai

安装

作者的 README

打开 README

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

Local-first memory and knowledge graph for AI coding agents

Your agent stops re-reading files and re-deriving the same conclusions.

Your notes, code and secrets never leave your machine.

Demo

Watch the 30-second demo

The problem

A long session accumulates hard-won detail about why the code is the way it is. Then the context compacts and it is gone. Next session the agent re-reads the same files, re-derives the same conclusions, and bills you for the same tokens again.

CLAUDE.md does not scale past a few dozen lines, and it cannot answer *"what did we decide about X, and why?"*.

Turbo Quant Memory is an MCP server that gives the agent a persistent, searchable store it writes to while it works — decisions, lessons, patterns, session handoffs — plus a compact index of your Markdown. Retrieval returns ~220-character result cards rather than whole documents; the agent loads full content only when a card is not enough.

Why this one

	Turbo Quant Memory	mem0 / OpenMemory	MCP `memory` server
Where your data lives	your disk, always	vendor cloud or self-host	your disk
Your data leaves the host	never	yes, unless self-hosted	never
Retrieval	hybrid BM25 + dense vector, RRF-fused	dense vector	exact graph lookup
What a search returns	compact cards, hydrate on demand	full memories	full nodes
Knowledge graph	yes — with lifecycle + linting	no	yes
Non-English content	Cyrillic exact-match out of the box	varies	n/a
Measures its own savings	yes — `server_info()`	no	no
Price	free, MIT	paid tiers	free

No HTTP client, no telemetry, no phone-home. Verify it yourself — this returns nothing:

grep -rnE '^[[:space:]]*(import|from)[[:space:]]+(requests|httpx|aiohttp|urllib3)\b' src/

To be precise about the one exception: on first run fastembed downloads the embedding model (~0.22 GB) from Hugging Face. After that the server runs fully offline. Your notes, code and secrets are never transmitted anywhere — there is nothing in the package that could send them.

Install

Let your agent install it

Paste this into Claude Code, Codex, Gemini CLI, Cursor or Antigravity:

Install and configure the Turbo Quant Memory MCP server for this workspace from

https://github.com/Lexus2016/turbo_quant_memory — follow the README, register the

tqmemory server, run turbo-memory-mcp skill install, run the health check, and

index this project.

skill install copies an operating manual into every agent skill directory on the machine, so every future session already knows how to use the memory without being told.

Or install it yourself

uv tool install turbo-quant-memory

Upgrading from 0.27.x or earlier? The distribution was renamed in 0.28.0, so uv tool upgrade turbo-memory-mcp no longer resolves — run uv tool install --force turbo-quant-memory once, and uv tool upgrade turbo-quant-memory afterwards. The turbo-memory-mcp command itself is unchanged, so client configs keep working.

Then register the server with your client:

claude mcp add --scope project tqmemory -- turbo-memory-mcp serve   # Claude Code

codex mcp add tqmemory -- turbo-memory-mcp serve # Codex gemini mcp add tqmemory turbo-memory-mcp serve # Gemini CLI

Cursor, OpenCode, Antigravity and other clients → CLIENT_INTEGRATIONS.md. Hermes runs MCP through a systemd gateway → docs/hermes.md.

📈 It measures its own savings — see for yourself

Turbo Quant Memory doesn't just *claim* to save tokens — every install keeps a running tally you can read anytime with server_info() (field usage_stats.headline). The savings are yours to verify, not ours to promise.

Live snapshot from a real developer instance (v0.28.2):

What the memory did	Number
🔢 Input tokens saved (cumulative)	≈ 2,640,000 and counting
🔁 Retrievals served	2,280 searches + 280 deep hydrations
📉 Average saved per retrieval	≈ 1,200 tokens
📚 Knowledge under management	237 active notes + 763 indexed code blocks
🛡️ Integrity	0 corrupted records · 0 pending migrations

These are one machine's cumulative numbers, not a synthetic benchmark — your own counter starts at zero and grows as your agent works. Run server_info() on your install to see your real figure.

What it does

Typed notes. decision, lesson, pattern, handoff — each stored with tags, provenance and a knowledge-graph link to the file or issue it is about.
Tiered memory. durable (decisions, patterns) and reference (indexed docs) are searched by default; episodic (session handoffs) stays out of the way until you ask for it, so yesterday's noise never buries an architectural decision.
Hybrid retrieval. A dense vector lane leads; a BM25 lane rescues exact terms — function names, file paths, IDs — fused with Reciprocal Rank Fusion. Cyrillic and other non-English terms match exactly, case- and accent-insensitive, with no configuration.
Knowledge graph. Directed, timestamped relations between notes, files and issues. Search results carry the linked context inline, so the agent does not need a second lookup.
Human notes outrank agent notes. Anything you explicitly asked to remember is flagged human-explicit and ranks above the agent's own observations at equal relevance.
Encrypted secrets vault. Project-scoped, AES-256-GCM, structurally unreachable from search. → docs/secrets-vault.md
Runs on a small machine. The default embedder is ONNX via fastembed — no PyTorch, ~0.22 GB model, comfortable on 2 GB of RAM.
Several agents, one project — automatically. Agents working in the same git working tree see each other's sessions, announced work and recent file changes; while two or more of them share the tree, changes to text files are recorded so they can be restored. No setup.

Full technical detail → docs/features.md

Several agents in one project

If you run more than one agent in the same working tree, tqmemory connects them automatically. There is nothing to configure.

Agents see each other. workspace_status lists the active sessions, what each one announced it is working on (announce_work, finish_work) and which files changed recently. A session that made no tqmemory call for 30 minutes is listed under idle_sessions instead: it is not an active peer and its announced areas are left out of overlaps. Other tqmemory responses carry a short workspace note only when something new has happened, and never for a lone session. health and server_info always include a workspace diagnostics block.
Changes are recorded. While two or more sessions share a git working tree, the watcher records new versions of text files it sees change (up to 1 MiB each, skipping anything matched by .gitignore or .tqmemoryignore). Several quick writes in a row can be merged into one version. file_history lists the versions and restore_file brings one back; the restore is itself undoable. The same is available from a terminal: turbo-memory-mcp files log and turbo-memory-mcp files restore.
Limits. Versions are recorded only while two or more sessions share a git working tree. The journal never runs outside a git working tree, in your home directory or at a filesystem root. Defaults: 1 MiB per file, a 256 MiB per-project size target and 14 days of retention. Recorded versions stay recoverable for 14 days; past that, or when the project is over its size target, the oldest are removed. The newest version of each file changed in the last 24 hours is never dropped for size. These defaults are set by TQMEMORY_JOURNAL_MAX_FILE_BYTES, TQMEMORY_JOURNAL_MAX_BYTES and TQMEMORY_JOURNAL_RETENTION_DAYS; the size limit is a target, not a hard maximum.

This is partial protection, not a guarantee that every change is saved. It does not block writes: two agents can still overwrite each other's work, and tqmemory can only show it and help you recover. Agents that never call tqmemory see nothing. It works on one computer only. To turn it off, set TQMEMORY_WORKSPACE_DISABLE=1.

The 24 MCP tools

Group	Tools
Write	`remember_note` · `deprecate_note` · `promote_note` · `index_paths`
Read	`semantic_search` · `hydrate` · `recent_context` · `list_scopes`
Graph	`link_entities` · `unlink_entities` · `get_related_entities`
Hygiene	`lint_knowledge_base` · `health` · `self_test` · `server_info`
Vault	`set_secret` · `get_secret` · `list_secrets` · `delete_secret`
Workspace	`announce_work` · `finish_work` · `workspace_status` · `file_history` · `restore_file`

Documentation


MEMORY_STRATEGY.md	How to actually use the memory day to day
CLIENT_INTEGRATIONS.md	Per-client setup: Cursor, OpenCode, Antigravity, …
TECHNICAL_SPEC.md	Architecture and storage format

| [docs/featur

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