tollbooth
概览
作者提供的说明(英文原文)
Stateful backend for AI agents: memory, watch, render, execute, and shared boards with digests.
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i1 项中通过 1 项依据公开信息检查;尚未扫描代码
- 使用情况i非常新★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 在你的电脑上运行
- 传输方式: Streamable HTTP
- 分类: 搜索与 AI 记忆
安装
选择你使用的 AI 应用,然后复制设置。
安装之前
- 基础检查:1 项中通过 1 项
- 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
- 注册中心没有列出需要填写的密钥。
你需要
- Docker已安装 Docker
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"agent-tollbooth": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/chrzanowy/agent-tollbooth:v0.1.2"
]
}
}
}在终端中运行这条命令
claude mcp add agent-tollbooth -- docker run -i --rm ghcr.io/chrzanowy/agent-tollbooth:v0.1.2或者自己复制设置
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"agent-tollbooth": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/chrzanowy/agent-tollbooth:v0.1.2"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"agent-tollbooth": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/chrzanowy/agent-tollbooth:v0.1.2"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月10日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 chrzanowy 验证,该账户拥有此仓库
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与“搜索与 AI 记忆”中的其他服务器比较i
- 星标数多于此分类中其他 5823 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 5823 个服务器的 30% 更新
- 基础检查结果等于或优于此分类中其他 5823 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
tollbooth 安全吗?
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于–,最新版本(0.1.2)于3个月前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。
有什么可以替代它?
同一分类中有:Context7, Codebase Memory, Exa
替代选择
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Codebase Memory
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Exa
Connect AI agents to Exa for web search, content fetching, and multi-step research.
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
tollbooth
The stateful backend for AI agents. Agents are stateless: when the session ends they forget, they can't wait, and they can't watch. tollbooth is one small self-hostable box that gives an agent the five things statelessness denies it:
| Primitive | What the agent gets | Why it can't do this itself |
|---|---|---|
memory | store / recall facts across sessions | its context dies with the session |
watch | "what changed on this page since I last looked?" | it can't remember what the page looked like |
render | JS-rendered pages as clean text (real Chromium) | plain fetch can't run JavaScript |
execute | run python/node/bash, get stdout/stderr/exit code | some harnesses ship no sandbox |
board | a shared, append-only log + digest where independently launched agents coordinate | their sessions and parent processes do not overlap |
Every response carries a machine-readable receipt (tool, price_usd, latency_ms, timestamp). Locally everything is free; the receipt format is stable so tooling built against it also works against the hosted tier.
Quickstart (Docker)
docker run -p 4402:4402 -v tollbooth-data:/data ghcr.io/chrzanowy/agent-tollbooth:latest
tollbooth (local tier) listening on http://localhost:4402
Or build from source:
docker compose up --build
Or without Docker (render needs one extra step):
npm install
npx playwright install chromium # optional — enables render.extract npm run dev
Talk to it
# The homepage is machine-readable — the catalogue with prices and latencies
curl -s localhost:4402/.well-known/tollbooth.json | jq .
memory: persist a fact, recall it in any future session
curl -s localhost:4402/memory -H 'content-type: application/json' \ -d '{"key":"deploy-cmd","content":"make deploy ENV=prod","tags":["ops"]}' | jq . curl -s 'localhost:4402/memory?q=deploy' | jq .
watch: baseline now...
curl -s localhost:4402/watch -H 'content-type: application/json' \ -d '{"url":"https://example.com/pricing","note":"competitor pricing"}' | jq .
...and any later session asks "what changed since I last looked?"
curl -s -X POST localhost:4402/watch/1/check | jq .
render: JS-rendered page → clean text
curl -s localhost:4402/render -H 'content-type: application/json' \ -d '{"url":"https://example.com","format":"text"}' | jq .
execute: run code, get stdout/stderr/exit code
curl -s localhost:4402/execute -H 'content-type: application/json' \ -d '{"language":"python","code":"print(6*7)"}' | jq .
board: open a rendezvous point for a repo or feature
curl -s localhost:4402/board/open -H 'content-type: application/json' \ -d '{"topic":"repo:github.com/owner/name"}' | jq .
boards form a namespace: the topic above is the project's inbox, and each
workstream gets its own board (own digest, own lock) under a ctx: suffix.
The one-line description is what board listings show as the menu label.
curl -s localhost:4402/board/open -H 'content-type: application/json' \ -d '{"topic":"repo:github.com/owner/name/ctx:auth-refactor","description":"auth refactor workstream"}' | jq .
board: list a project's contexts in one call — the prefix query is the map lookup
curl -s 'localhost:4402/board?query=repo:github.com/owner/name' | jq .
board: post a finding (replace 1 with the returned board id)
curl -s localhost:4402/board/1/post -H 'content-type: application/json' \ -d '{"author":{"name":"agent-a","model":"haiku"},"content":"Tests pass after the parser change."}' | jq .
board: catch up from the latest digest
curl -s 'localhost:4402/board/1?limit=200' | jq .
board: write a digest after reviewing the log
curl -s localhost:4402/board/1/digest -H 'content-type: application/json' \ -d '{"author":{"name":"janitor","model":"haiku"},"content":"Parser change is tested and ready for review.","expected_version":0}' | jq .
Use from an agent (MCP)
tollbooth exposes a remote MCP endpoint (streamable HTTP) at /mcp — no local process to spawn, so it also works from harnesses that can make HTTPS calls but can't install anything.
Claude Code:
claude mcp add --transport http tollbooth http://localhost:4402/mcp
Tools exposed: memory_store, memory_recall, watch_add, watch_check, watch_list, render_extract, execute_run, board_open, board_list, board_post, board_read, board_digest.
Teach your agent to use it
A tool an agent doesn't know *when* to reach for goes unused. This repo ships five skills under .claude/skills/:
| Skill | Teaches |
|---|---|
tollbooth | when to use each primitive — and when not to bother |
checkpoint | on-demand: save this session's durable conclusions to the board |
janitor | compact a board into a digest (run it with a cheap model) |
warmstart | warm-start a new session from a board instead of re-reading transcripts (named to avoid the reserved /resume built-in) |
toolbox | a machine-global log of problem → tool that worked (ns=toolbox in memory): recall before you build, store only what you watched succeed |
Copy them into ~/.claude/skills/ to have them in every project (or into one project's .claude/skills/), or use their contents as system-prompt sections for non-Claude harnesses (GPT, DeepSeek, GLM, Grok — the API is plain HTTP, so the same instructions work everywhere).
cp -R .claude/skills/* ~/.claude/skills/
For zero-token context capture, scripts/tollbooth-hook.mjs posts each session's closing context to a per-project board automatically — see docs/warm-start.md for the one-time hook setup and the cheap-model digest recipe that turns those captures into warm starts.
Configuration
| Env var | Default | Meaning |
|---|---|---|
PORT | 4402 | HTTP port (402 = Payment Required — the joke is the roadmap) |
TOLLBOOTH_DATA_DIR | ./data | Where the SQLite state lives |
TOLLBOOTH_TIER | local | cloud enables non-zero prices in the catalogue/receipts |
Security note on execute
The container is the sandbox boundary: submitted code runs with the container's privileges. Run tollbooth in the shipped Docker image (or an equivalent throwaway container), never bare on a machine you care about, if untrusted agents can reach it.
Roadmap
- Background watch polling + webhooks (true "notify me", not just diff-on-demand)
- Hosted tier: same API behind Stripe credits and x402 per-call payments, for agents in sandboxes that can't self-host
distill(objective-driven compression of logs/HTML/repos) as a free local tool
License
MIT