claw-tsaver
claw-tsaver
专为 OpenClaw 用户设计的节省 Token 的 MCP 代理。通过延迟展开技术,将工具调用负载减少 90% 以上。
为什么使用它
MCP 工具调用通常会在单次响应中返回数千个 Token 的 HTML 或 JSON 数据,但模型通常只使用其中的 5%。剩下的 95% 会在无形中消耗上下文窗口并增加成本。claw-tsaver 位于 OpenClaw 和您的下游 MCP 服务器之间,拦截过大的响应,并向模型提供紧凑的预览和按需获取的句柄。
Related MCP server: TokenSaver MCP
如何工作
sequenceDiagram
participant U as OpenClaw (Claude)
participant C as claw-tsaver proxy
participant F as fetch / puppeteer / etc.
U->>C: call_tool("fetch", url)
C->>F: forward call
F-->>C: 11,507 tokens of HTML
Note over C: tiktoken count > threshold
C->>C: store full content in SQLite
C-->>U: {preview_head, preview_tail, expand_handle}<br/>(only 104 tokens)
Note over U: model decides if it needs full text
U->>C: expand_content(handle)
C-->>U: full 11,507 tokens实际测量
测试 | 原始 Token 数 | 返回 Token 数 | 节省比例 |
获取维基百科 "Tokenization (data security)" | 11,507 | 104 | 99.1% |
测试环境:OpenClaw + Claude Sonnet 4.6 + mcp-server-fetch,2026-04-25。
原始数据:benchmarks/mvp-day1-fetch.jsonl。
快速开始
1. 前置要求
安装 uv(仅需设置一次):
curl -LsSf https://astral.sh/uv/install.sh | sh无需安装 claw-tsaver —— uvx 会按需获取并运行它。
2. 配置下游 MCP 服务器
编辑 ~/.claw-tsaver/config.json(首次运行 claw-tsaver-mcp 时会自动创建模板):
{
"downstream_servers": [
{"name": "fetch", "command": "uvx", "args": ["mcp-server-fetch"]}
],
"compression_threshold_tokens": 500
}3. 在 OpenClaw 中注册
在 ~/.openclaw/openclaw.json 的顶层添加此代码块:
"mcp": {
"servers": {
"claw-tsaver": {
"command": "uvx",
"args": ["--from", "git+https://github.com/Yang1Bai/claw-tsaver",
"claw-tsaver-mcp"]
}
}
}然后重启 OpenClaw 网关:openclaw gateway restart
仪表盘
可选:用于实时查看 Token 节省统计数据的本地 Web UI。
uvx --from git+https://github.com/Yang1Bai/claw-tsaver claw-tsaver-dashboard在浏览器中打开 http://localhost:7878。
路线图
[x] 模块 A:延迟展开代理(本次发布)
[x] 模块 D:本地仪表盘(本次发布)
[ ] 模块 B:工具路由(每轮仅自动加载相关的 MCP)
[ ] 模块 C:对话历史压缩(原子事实卡片)
许可证
MIT — 详见 LICENSE 文件。
贡献
欢迎提交 Issue 和 PR。
Available Tools
1 toolexpand_contentA
Retrieve the full content of a previously compressed tool result. Pass the expand_handle returned in the compressed envelope.
| Name | Required | Description | Default |
|---|---|---|---|
| handle | Yes | The expand_handle from a compressed result. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description implies a read operation but does not detail any side effects, auth requirements, or handle expiration.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two efficient sentences front-load the purpose with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter tool with no output schema, the description sufficiently guides usage, though output format is unstated.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds context that the handle comes from a compressed envelope, complementing the schema's parameter description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves the full content of a compressed result, using specific verb and resource.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description instructs to pass the expand_handle from a compressed envelope, implying the usage context, but lacks explicit conditions or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v0.0.1- First observed
expand_content
TDQS
Scored across 1 tool
Only one tool exists, so there is no potential for confusion between different tools.
With a single tool, there is no naming inconsistency to evaluate; the name 'expand_content' is clear and descriptive.
A single tool for expanding compressed results is very thin; the server likely needs additional tools (e.g., for listing handles) to be useful as an MCP server.
The tool covers its stated purpose of retrieving full content, but the server lacks any supporting tools for compression or handle management, leaving a minor gap in the overall surface.
Maintenance
Related MCP Connectors
An MCP memory server. One memory your agents share — across models, devices and apps.
MCP server for building and testing AI agents with multi-model experimentation and insights.
Persistent memory for AI agents to retain, retrieve, and recall conversation context through MCP.
Cloud-hosted MCP server for durable AI memory
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that helps AI agents reduce token usage by converting data to TOON format and stripping comments and unnecessary whitespace from code files.31 PyPIMIT
- AlicenseAqualityDmaintenanceAn MCP server that reduces AI API costs by up to 97% through token measurement, compression, caching, and pruning, all without changing prompts.101Apache 2.0
- AlicenseAqualityBmaintenanceAn MCP server that intelligently filters and compresses tool outputs to reduce context window usage, saving up to 90% of tokens by removing noise such as passing tests and redundant information.512 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server that reduces AI agent token usage by up to 90% through intelligent context compression. Enables efficient code exploration, multi-file refactoring, and debugging by providing tools for smart reading, searching, and managing code context.4MIT