by mcp-shark · MCP Server · ★ 24
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. does it as a single Go binary with a local SQLite catalog. No containers, no API keys for the tool layer, no infrastructure. That's it.
| Stars | 24 |
| Forks | 2 |
| Language | Go |
| Category | MCP Server |
| License | MIT |
| Quality Score | 74.3433672305761/100 |
| Last Updated | 2026-05-10 |
| Created | 2026-03-29 |
| Platforms | browser, cli, go, mcp |
| Est. Tokens | ~14k |
Explore other popular mcp server tools:
lazy-tool is local-first MCP discovery runtime for agents — search before invoke, reduce prompt bloat, and route to local MCP tools. It is categorized as a MCP Server with 24 GitHub stars.
lazy-tool is primarily written in Go. It covers topics such as agent-tools, ai-agents, cli.
You can find installation instructions and usage details in the lazy-tool GitHub repository at github.com/mcp-shark/lazy-tool. The project has 24 stars and 2 forks, indicating an active community.
lazy-tool is released under the MIT license, making it free to use and modify according to the license terms.