你连接的MCP服务器越多，每个提示中被大量倾倒的工具模式也越多。模型读取所有这些方案，更频繁地选择错误的，你为每个令牌付费。这是一个已知的问题——解决方法（先搜索后调用）已经被广泛采用。

大多数这种模式的实现都需要 Python 栈、矢量数据库、Docker 或云服务。lazy-tool 则以单一的 Go 二进制文件和本地 SQLite 目录实现。没有容器，没有工具层的 API 密钥，也没有基础设施。

就这些。一个二进制文件，读取你现有的IDE配置，本地索引所有内容，作为MCP端点。

llama-3.1-8b-instant，每个任务重复20次。方法论

---

适合的地方

有几个项目以不同方式解决MCP工具的蔓延问题：RAG-MCP（Python + vector DB）、MetaMCP（Docker）、AWS AgentCore Gateway（托管云）以及Claude Code内置工具搜索（客户端，仅Claude）。

lazy-tool

The more MCP servers you connect, the more tool schemas get dumped into every prompt. The model reads all of them, picks the wrong one more often, and you pay for every token. This is a known problem — the pattern that solves it (search before invoke) is well-established.

Most implementations of that pattern require a Python stack, a vector database, Docker, or a cloud service. lazy-tool does it as a single Go binary with a local SQLite catalog. No containers, no API keys for the tool layer, no infrastructure.

make build → import --write → reindex → serve

That’s it. One binary, reads your existing IDE config, indexes everything locally, serves as an MCP endpoint.

llama-3.1-8b-instant, 20 repeats per task. Methodology

---

Where it fits

Several projects address MCP tool sprawl in different ways: RAG-MCP (Python + vector DB), MetaMCP (Docker), AWS AgentCore Gateway (managed cloud), and Claude Code’s built-in tool search (client-side, Claude-only).

lazy-tool occupies a specific niche: local-first, zero-dependency, single binary.

• No infrastructure. One Go binary, local SQLite. No Docker, no vector DB service, no cloud account.
• IDE auto-import. Reads your Claude Desktop, Cursor, or VS Code MCP config. No manual YAML unless you want it.
• Three modes in one tool. Direct mode (transparent proxy) for simple setups and smaller models, search mode (5 meta-tools) for large catalogs with strong models, hybrid for both. Switch with a flag.
• Provider-agnostic. Not tied to Anthropic, OpenAI, or any specific client. Anything that speaks MCP over stdio or HTTP.
• Reliability built in. Circuit breaking, caching, session reuse, and tracing handled at the proxy layer.

If you’re already inside Claude Code and only use Claude, the built-in tool search may cover your needs. If you want something that works across providers, runs locally without dependencies, and aggregates multiple MCP servers — that’s the space lazy-tool is in.

---

Install

Quick install (pre-built binary)