This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Heku
Convert any API to MCP locally, Make agents grow their tools
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.
Hello all,
First off, thank you for taking the time to go through this.
My name is Ruchit and I build custom agent harnesses for different business domains. Across all the harness projects I've built so far, I kept feeling restricted by MCP — not because anything's wrong with the protocol, but because we've been implementing it from the wrong perspective.
So I built heku. Adding Postman, Jira, or Bitbucket capabilities to my agent is no longer a long list of steps, it's a few clicks through a config. Any API, whether it's your own product or something you use daily like GitHub, becomes an MCP tool through a hot-reloaded config.
The part I'm most excited about: agents can now correct their tools, not just call them. You can add new tools mid-session, pulling from a config I've already pre-seeded in the heku Hub registry. You can grow your API surface into MCP tools in seconds, in the same conversation.
I also added lazy discovery, so the manifest stays around 700 tokens. Those are just discovery tools that let the agent find and load the real tools when it needs them, instead of dumping everything into context up front.
It's Apache 2.0, install is npm i -g @rapidthoughtlabs/heku. I'm the solo builder behind it and I'll be around all day, would genuinely love your feedback, especially from anyone running MCP in production.
What's been your biggest friction with MCP so far?
About Heku on Product Hunt
“Convert any API to MCP locally, Make agents grow their tools”
Heku was submitted on Product Hunt and earned 6 upvotes and 4 comments, placing #84 on the daily leaderboard. 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.
On the analytics side, Heku competes within API, Open Source, Developer Tools and GitHub — topics that collectively have 723.7k followers on Product Hunt. The dashboard above tracks how Heku performed against the three products that launched closest to it on the same day.
Who hunted Heku?
Heku was hunted by ruchit nannavare. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Heku including community comment highlights and product details, visit the product overview.
ruchit nannavare