TOMC Memory

MCP文档知识

提供方 未标注

文档知识 未标注 会话登录 社区 / 第三方 Claude DesktopClaudeCursorVS Code

仅使用 CPU 的任务上下文压缩和可在代码代理与计算机之间复用的项目笔记,提供可选的动画桌面猫、上下文节省面板,以及有文档记录的实时模型测试。

一句话选型结论

按资料字段整理

TOMC Memory 属于文档知识类 MCP 服务器,传输方式未标注,会话登录,可直接接入 Claude Desktop、Claude、Cursor 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

支持客户端

适用场景

记忆

安装与配置

未标注 会话登录
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

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

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

知识库读写

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

内容整理

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

选择建议

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

值得选的地方

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

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

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

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
TOMC Memory当前 未标注 未标注 未标注 无 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

服务器档案

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

详细介绍

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

TOMC Memory

English | 简体中文 · v0.3.1 research preview · MIT · Python 3.10+

I got tired of re-explaining my project to every new AI chat, and then getting the old version of a decision back.

When a fact changes, only the latest version comes back.

Say your project chat moved from Flask to Django, then FastAPI, then Litestar. TOMC Memory hands your assistant framework = Litestar, plus the line it came from.

After installing, say to your assistant: "Try TOMC Memory". In a terminal: tomc try.

  • Latest value, offline check (v0.3.0): 144 questions per budget, each about a fact that changed 3 to 5 times. At the default budget the prepared context held the latest value every time (v0.2.1: 58%). At a 10% budget: 85% (v0.2.1: 51%). Synthetic notes and chats, no model call. We wrote these questions alongside the fixes, so treat them as our regression test, not an independent evaluation.
  • Smaller requests in Codex (0.1.0 preview, not re-run since): 9 synthetic project chats of about 10K to 40K tokens, 5 questions each, gpt-6.1-sol. Keeping 40% of the history cut request input by 29.7% on average, and all 45 answers stayed right. One run per condition.
  • BEAM long-history benchmark (paper experiments): same reader model on both sides, 3 readers, 6 other memory methods. TOMC had the higher mean score in 54 of 54 comparisons at 500K to 10M tokens, and 17 of 18 at 100K. Mean scores only; not comparable with other projects' BEAM numbers.

Every number, with its conditions and failures · Before you use it · Install

Before you use it

  1. It does not shrink the chat your assistant is already having. Claude Code and Codex manage their own chat. TOMC Memory works on history you hand it and notes you saved. Context ownership
  2. Short histories gain little. Under about 10K tokens there is not much to cut. With the default budget, our earlier tests saved roughly 10–20% of input (Codex 9.2%, Claude API-style 19.8%; 0.1.0 previews). Smaller budgets save more but can drop the latest value. Check them on your own tasks first. The default keeps 80% of a history up to 10K tokens, sliding to 60% at 1M, and never less than 1,024 tokens.
  3. It matches words, not meaning. A reworded update such as "scratch that, go with Django" can be missed, mostly at small budgets. When a later line may have changed a value, the value is marked STATE? and that line is attached so you or your assistant can check it.
  4. What gets stored, and how to erase it. Results of prepare_context and recall_memory are not saved unless you turn it on (tomc settings --save-mcp-results on). Notes you save with remember_memory stay on your computer in ~/.tomc/memory.sqlite3. Delete one notebook with forget_memory, or everything with tomc erase-all --yes. Security and privacy
  5. Not every client is checked. Codex and Claude Code passed real model calls with earlier previews. For Cursor, TRAE and WorkBuddy the setup is written, but their tool calls have not been checked on real machines. Claude Desktop installation has not been checked in the app.
  6. The paper is not public yet. The benchmark numbers come from our own runs and setup. The evidence page lists sources, sample sizes and what can be rechecked offline (make reproduce).

Install

Each path ends the same way: say "Try TOMC Memory" in a new chat, and run tomc doctor if something looks wrong. The Claude Code and Codex plugins need uv. Running from source needs Python 3.10 or newer (python3 --version; the macOS system Python 3.9 is too old).

Claude Code```text

/plugin marketplace add ZipengWu365/TOMC
/plugin install tomc-memory@tomc


Start a new session, check `/mcp` for `plugin:tomc-memory:tomc`, then say "Try TOMC Memory" or run `/tomc-memory:try`. More Claude Code notes

### Codex

Download tomc-memory-codex-0.3.1.zip, unzip it into a folder you will keep, and run there:```bash
uv run --no-project --python 3.12 install.py --check
uv run --no-project --python 3.12 install.py

The installer starts the server once to check it. Open a new Codex session and say "Try TOMC Memory". Full Codex steps

Any MCP client (Cursor, Claude Desktop, WorkBuddy, TRAE …)```bash

git clone https://github.com/ZipengWu365/TOMC.git && cd TOMC
python3 -m venv .venv && .venv/bin/python -m pip install -e '.[mcp]'
.venv/bin/tomc setup --client cursor --write # or claude-desktop, claude-code, codex, workbuddy
.venv/bin/tomc doctor


`--write` backs up the client's config file first and keeps your other servers. For TRAE or a project file, add `--config path/to/mcp.json`. Restart the client and say "Try TOMC Memory". On Windows use `py -3.12 -m venv .venv` and `.venv\Scripts\`. Per-client guides

### Python API```python
from tomc import prepare_context  # pip install -e . from a clone; no dependencies

prepared = prepare_context(history, task)
response = client.chat.completions.create(model=model, messages=prepared.messages)

Send prepared.messages in place of the old history; appending it adds input. .venv/bin/tomc try shows a worked example offline. API guide

Mainland China network

If GitHub or PyPI downloads stall, use a mirror for pip and uv:bash python3 -m pip install --user uv -i https://pypi.tuna.tsinghua.edu.cn/simple export UV_DEFAULT_INDEX=https://pypi.tuna.tsinghua.edu.cn/simple export UV_PYTHON_INSTALL_MIRROR=https://registry.npmmirror.com/-/binary/python-build-standalone python3 -m uv run --no-project --python 3.12 install.py # Codex installer, run in the unzipped folder

For a source install, add -i https://pypi.tuna.tsinghua.edu.cn/simple to the pip install line. In PowerShell, set the variables with $env:UV_DEFAULT_INDEX="…".

Go deeper

  • Evidence and claims ledger: every number, its source file, model, sample size and version, plus the negative results.
  • Switch assistants and keep your notes: save in Codex, continue in Claude Code, on one computer.
  • Desktop companion (beta): a small cat that shows today's estimated context reduction and makes a weekly report card you can share; Windows and macOS. The optional request gateway is Windows only. Linux has the plugins and MCP server only.
  • Video overview (1:37). One Codex number in the video has no protocol in this repository; see media notes.

Community, citation and license

Try, compare, contribute: First-run reports · Context-compression evaluation note · Contribution guide

Follow Zipeng Wu for work across time-series research software and AI task memory. Star this repository to save TOMC; use Watch settings for project notifications. Following or starring is optional and is never required for help.

Cumulative clones · recorded since 2026-10-02 · updated 2026-11-19 UTC. Method and updates

MIT License: free to use, change and ship, including commercially; keep the copyright and license notice. If TOMC Memory helps your research, please cite it with CITATION.cff (GitHub's "Cite this repository" button). Examples are synthetic; the repository holds numeric benchmark aggregates only, without question text, answers or API payloads. Data provenance · Data and licensing

常见问题

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

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

TOMC Memory 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

TOMC Memory 收费吗?

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

TOMC Memory 需要 API Key 吗?

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

TOMC Memory 支持哪些客户端?

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

TOMC Memory 能提供哪些能力?

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

热门专题

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

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