英文 |Русский

将噪声较大的OpenAPI和MCP工具表面编译为一个较小的、受控的运行时表面，用于LLM代理。

今天通过真实的OpenRouter模型运行、真实保存的基准测试成果和实时OpenAPI调用检查进行了验证。

今天最适合的：

• 使用VS Code的用户MCP服务器过多
• OpenAPI 或 MCP 重代理栈
• 希望减少暴露工具表面且不重写平台的团队

安装

支持v1.0.0的两条路径：

1. 从 GitHub Releases 下载预建的归档
2. 用 Go 从源头安装

在 v1.0.0 标签作为最新标签发布后，这也适用：

v1.0.0的发布资源：

• toolc_v1.0.0_windows_amd64.zip
• toolc_v1.0.0_linux_amd64.tar.gz
• toolc_v1.0.0_linux_arm64.tar.gz
• toolc_v1.0.0_darwin_amd64.tar.gz
• toolc_v1.0.0_darwin_arm64.tar.gz
• SHA256SUMS.txt

VS 代码快速入门

如果你已经在VS Code中使用MCP，可以从这里开始。

toolc 可以将你已有使用的 MCP 配置编译成一个更小的受控表面，成为你的代理看到的唯一 MCP 服务器。

从这里开始：

1. 建造toolc
2. 优化你现有的MCP配置
3. 将扩展对准已发布的配置

toolc

English | Русский

Compile noisy OpenAPI and MCP tool surfaces into one smaller governed runtime surface for LLM agents.

Validated today with real OpenRouter model runs, real saved benchmark artifacts, and a live OpenAPI invoke check.

Best fit today:

• VS Code users with too many MCP servers
• OpenAPI or MCP-heavy agent stacks
• teams that want less exposed tool surface without a platform rewrite

Install

Two supported paths for v1.0.0:

1. download a prebuilt archive from GitHub Releases
2. install from source with Go

go install github.com/aak204/Tool-Catalog-Compiler/cmd/[email protected]

After the v1.0.0 tag is published as the latest tag, this also works:

go install github.com/aak204/Tool-Catalog-Compiler/cmd/toolc@latest

Release assets for v1.0.0:

• toolc_v1.0.0_windows_amd64.zip
• toolc_v1.0.0_linux_amd64.tar.gz
• toolc_v1.0.0_linux_arm64.tar.gz
• toolc_v1.0.0_darwin_amd64.tar.gz
• toolc_v1.0.0_darwin_arm64.tar.gz
• SHA256SUMS.txt

VS Code Quickstart

If you already use MCP in VS Code, start here.

toolc can take the MCP config you already use, compile it into one smaller controlled surface, and become the single MCP server your agent sees.

Start here:

1. build toolc
2. optimize your existing MCP config
3. point your extension at the emitted config
4. run one toolc mcp-serve surface instead of many raw servers

Build once:

PowerShell

./scripts/build.ps1

bash

./scripts/build.sh

Common input config paths:

• VS Code / Codex-style MCP config: .vscode/mcp.json
• Roo Code project config: .roo/mcp.json
• Roo Code global config: mcp_settings.json
• Cline config: cline_mcp_settings.json
• Kilo config: kilo.jsonc or .kilocode/mcp.json

Optimize an existing MCP config:

PowerShell

./dist/toolc.exe optimize-mcp `
  -input .vscode/mcp.json `
  -emit vscode `
  -out-dir dist/mcp-optimized

bash

./dist/toolc optimize-mcp \
  -input .vscode/mcp.json \
  -emit vscode \
  -out-dir dist/mcp-optimized

What you get:

• dist/mcp-optimized/toolc.compiled.json
• dist/mcp-optimized/optimized.json
• dist/mcp-optimized/optimization-report.json

Use it:

• point your extension at dist/mcp-optimized/optimized.json
• the emitted config starts toolc mcp-serve for you