Launching today
Heku
Convert any API to MCP locally, Make agents grow their tools
11 followers
Convert any API to MCP locally, Make agents grow their tools
11 followers
heku turns MCP servers into a config file. No more custom auth, transport, and tool boilerplate for every API you plug into an agent. Point it at an HTTP API, a database, gRPC, or another MCP server. A tiny manifest exposes config dicovery tools first, so the LLM lazily discovers tools only when needed. Context stays lean, credentials stay isolated, tools hot-reload mid-session. Apache 2.0. The boilerplate harness I kept rewriting by hand.
How does tool hot-reloading mid-session actually work without confusing the model mid-conversation, especially when schemas change?
@fatmanurcink2r Heku only exposes 3-4 tools for discovery of the tools from the configs it manages. Only you know what capabilities your model has, agent then uses to 4 tools to implicitly discover exact tools it need to call using heku search tool and makes the call to that tool. This allows a tiny manifest but also makes heku a black box to your agent. If you are building a bespoke solution, you call list_config tool and save its result into the system prompt and make sure it refresh the tool call before next user message comes in, that way your agent will always remain updated what configs it has already which will also bring down the tool calls needed to search the right tool. Hope this helps!
the lazy discovery via a tiny manifest is genuinely clever, keeps the context window from bloating when you point it at a dozen APIs. love that credentials stay isolated too.