接入你的智能体
發布者自己的指令。不是 PlugMCP 端點。
用我們的金鑰與日誌託管一份副本。
uvx turbo-quant-memory==0.36.1Claude Code 沒有本機指令的安裝連結。複製下方指令並在終端機中執行。
TQMEMORY_FTS_LANGUAGE=<value> TQMEMORY_EMBEDDING_BACKEND=<value> TQMEMORY_MIGRATE_ON_STARTUP=<value> TQMEMORY_SECRETS_PASSPHRASE=<secret> claude mcp add io.github.lexus2016-turbo-quant-memory -- uvx turbo-quant-memory==0.36.1在終端機中執行。
{ "mcpServers": { "io.github.lexus2016-turbo-quant-memory": { "command": "uvx", "args": [ "turbo-quant-memory==0.36.1" ], "env": { "TQMEMORY_FTS_LANGUAGE": "<value>", "TQMEMORY_EMBEDDING_BACKEND": "<value>", "TQMEMORY_MIGRATE_ON_STARTUP": "<value>", "TQMEMORY_SECRETS_PASSPHRASE": "<secret>" } } }}claude_desktop_config.json
遠端 URL 還是本機指令？ 兩種安裝方式的差異
來自發布者
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?".
Local-first memory and knowledge graph for coding agents. Compact retrieval, no network.
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.
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.
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
tqmemoryserver, runturbo-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.
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.
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):
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.
decision, lesson, pattern, handoff — each stored with tags, provenance and a knowledge-graph link to the file or issue it is about.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.human-explicit and ranks above the agent's own observations at equal relevance.Full technical detail → docs/features.md
If you run more than one agent in the same working tree, tqmemory connects them automatically. There is nothing to configure.
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..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.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.
MIT. Copy it, modify it, fork it, ship it inside a closed-source product, sell it. Attribution is the only condition.
🇺🇸 English · 🇺🇦 Українська · 🇷🇺 Русский
Local-first memory and knowledge graph for coding agents. Compact retrieval, no network.
{ "mcpServers": { "io.github.lexus2016-turbo-quant-memory": { "command": "uvx", "args": [ "turbo-quant-memory==0.36.1" ], "env": { "TQMEMORY_FTS_LANGUAGE": "<value>", "TQMEMORY_EMBEDDING_BACKEND": "<value>", "TQMEMORY_MIGRATE_ON_STARTUP": "<value>", "TQMEMORY_SECRETS_PASSPHRASE": "<secret>" } } }}工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式，而不是 PlugMCP 代理伺服器。
發布者列出了以下環境變數：TQMEMORY_FTS_LANGUAGE, TQMEMORY_EMBEDDING_BACKEND, TQMEMORY_MIGRATE_ON_STARTUP, TQMEMORY_SECRETS_PASSPHRASE。
Turbo Quant Memory 透過 stdio 在本機執行。
上次檢查時間：2026-11-14。 Local-first memory and knowledge graph for coding agents. Compact retrieval, no network.