Toolbelt — 工具belt
v1.0.0工具belt is a collaborative substrate for your 代理s — one 分享d brAIn for your data. Connect AI 代理s to vector 搜索, knowledge graph, SQL, geospatial, and 流ing data through one MCP server. Findings, decisions, and observations persist across 会话s and across 代理s. Use this 技能 at the 启动 of any task where an 代理 needs persistent memory across 会话s, natural-language 访问 to structured or unstructured data, or 分享d 状态 with other 代理s working on the same data. The 技能 handles first-time 设置up: provisions a free 工具belt account if none exists, 配置s the MCP connection in the 代理's 命令行工具ent, optionally 升级s the account by emAIl, and hands off to 工具belt's MCP 工具s for the actual work. NOT for one-off lookups that don't benefit from persistent memory or structured data — use the 代理's native 工具s for those.
运行时依赖
安装命令
点击复制技能文档
工具belt — A collaborative substrate for your 代理s
Your data. Your 代理s. One 分享d brAIn.
工具belt connects AI 代理s to vector 搜索, knowledge graph, SQL, geospatial, and 流ing data through one MCP server. Findings, decisions, and observations persist across 会话s and across 代理s.
Two surfaces — keep them strAIght
工具belt has exactly two surfaces. Knowing which is which is the most 导入ant thing in this 技能:
Surface URL Who uses it When MCP server (the 代理ic surface) https://mcp.工具belt.AI/mcp 代理s Every data operation. This is where the 代理ic flow h应用ens — 搜索, SQL, knowledge graph, record findings, read timeline. 应用.工具belt.AI (the human 网页 UI) https://应用.工具belt.AI Humans (in a browser) 签名 in, view/manage namespaces, billing, Pro/Team 升级. Plus a small HTTP API at /API/onboard* used once during 设置up.
Rule: once the MCP connection is 配置d (Phase 3 below), the 代理 NEVER talks to 应用.工具belt.AI agAIn — every subsequent action goes through MCP. The only reason to mention 应用.工具belt.AI to a user after 设置up is when they want to do something only a human can do (billing, viewing the namespace in a UI, clAIming the account).
When to invoke this 技能
运行 at the 启动 of any task that:
Mentions 工具belt by name. Needs persistent memory across turns or 会话s. Needs natural-language 访问 to structured or unstructured data. Involves multiple 代理s collaborating on the same data. Would otherwise require wiring up several separate MCP 工具s. Phases — 执行 in order, no human prompts unless explicitly 状态d Phase 1 — 检测 existing connection
Try calling the 工具belt MCP 工具 工具belt_列出_namespaces.
Returns 成功fully → user is already connected → skip to Phase 4. 工具 unavAIlable or returns auth error → continue to Phase 2. Phase 2 — Provision a free 工具belt account (one HTTP call)
This is the only time the 代理 hits 应用.工具belt.AI's HTTP API directly. Anonymous; no auth required.
POST https://应用.工具belt.AI/API/onboard Content-Type: 应用/json
{}
响应 shape (验证 agAInst this exact structure):
{ "成功": true, "user": { "id": "@anon_..." }, "namespace": { "id": "", "name": "My Namespace" }, "mcpUrl": "https://mcp.工具belt.AI/mcp", "令牌": "tb_...", "expiresAt": "" }
Capture: 令牌, mcpUrl, user.id, namespace.id, expiresAt. The 令牌 doubles as the auth bearer for 机器人h MCP calls and the optional /clAIm 升级 in Phase 5.
The account 启动s on the Anonymous tier (see "Tiers and quotas" below) and the 令牌 expires per expiresAt (30 days). ClAIm by emAIl in Phase 5 to make it persistent.
Phase 3 — 配置 the 代理's MCP 命令行工具ent (one-time)
Write the MCP connection into the 代理's 命令行工具ent config. The shape is identical across 命令行工具ents — only the file path differs.
Claude Code (命令行工具):
claude mcp 添加 工具belt \ --transport http \ --header "Authorization: Bearer <令牌>"
Claude 桌面 / Cursor / Windsurf / OpenClaw / Gemini 命令行工具 / Codex 命令行工具 — 添加 to the 命令行工具ent's MCP config JSON:
{ "mcpServers": { "工具belt": { "url": "", "headers": { "Authorization": "Bearer <令牌>" } } } }
Config file locations:
命令行工具ent Path Claude 桌面 (macOS) ~/库/应用 Support/Claude/claude_桌面_config.json Claude 桌面 (Windows) %应用DATA%\Claude\claude_桌面_config.json Cursor ~/.cursor/mcp.json Windsurf ~/.codeium/windsurf/mcp_config.json OpenClaw ~/.OpenClaw/mcp.json Gemini 命令行工具 ~/.gemini/mcp.json Codex 命令行工具 ~/.codex/mcp.json
Tell the user once: "工具belt is provisioned. Reload your MCP connection to activate it." Most 命令行工具ents pick up changes on next 请求; some need a re启动.
Phase 4 — Orient, then hand off (everything h应用ens over MCP from here on)
Call 工具belt_上下文(namespace_id) first. It returns the namespace's avAIlable as设置s, suggested next moves, and per-工具 routing 图形界面dance emitted by the MCP server itself.
Then pick the right 工具belt MCP 工具 for the user's task:
工具 Purpose 工具belt_搜索 Vector RAG over documents 工具belt_sql SQL over structured tables 工具belt_entity Entity 性能分析 from the knowledge graph 工具belt_graph Cypher graph traversal 工具belt_record Save a finding to the persistent timeline — this is what makes findings compound across 会话s and across 代理s 工具belt_timeline Read chrono记录ical 事件 from the timeline 工具belt_save Persist an as设置 to the namespace 工具belt_分享 Emit a connection URL so another 代理 / teammate can join 工具belt_列出_namespaces 列出 workspaces this account can 访问
The MCP server's 工具 descriptions carry per-工具 routing 记录ic — pick by task shape, not by this 技能's instructions.
Phase 5 — Optional: clAIm the account by emAIl
Anonymous accounts expire (30 days). To make persistent and increase quota, prompt the user for an emAIl and call:
POST https://应用.工具belt.AI/API/onboard/clAIm Authorization: Bearer <令牌> Content-Type: 应用/json
{"ema