February 24, 2026
Two tools, infinite drama
Show HN: Declarative open-source framework for MCPs with search and execute
Two buttons to rule AI tools? Devs cheer, skeptics side-eye
TLDR: Hyperterse packs many AI tools behind just “search” and “execute,” promising simpler setups for developers. One Rails veteran rushed to integrate, while others debated simplicity versus control, cracking jokes and asking how debugging and discovery will really work — a big bet that could reshape how AI assistants use tools.
Hyperterse just dropped a bold promise: hide hundreds of AI tools behind two buttons — “search” and “execute” — and skip the “glue code” headache. It’s open source (Apache 2.0), with built-in auth, caching, and observability, aiming to make AI agents (think smart software helpers) way simpler to wire up. The crowd reaction? A mix of hype, side-eye, and memes. Rails OG obiefernandez practically sprinted in, pledging to plug this straight into Ruby on Rails and linking to prior work (medium.com/zar-engineering/code-mode-mcp-ac17c2a1038b). Fans shouted “finally!” at the idea of a single, consistent interface.
But the drama kicked off fast: skeptics grilled the “two tools only” approach — is collapsing everything behind search/execute genius or a debugging nightmare? Jokes flew (“search and ye shall execute”), while worrywarts asked how an agent won’t get lost digging through a hundred options. Supporters argued that discovery is the point, and that less boilerplate means more shipping; doubters demanded real-world benchmarks and clearer guardrails when agents go rogue. The split is classic: simplicity vs control. One camp sees two buttons to rule them all, the other sees a black box. Either way, the repo’s getting eyeballs and stars — and the Rails crew is already sharpening their tools.
Key Points
- •Hyperterse is an open-source framework for building MCP tool servers declaratively.
- •Agents only see two MCP tools—search and execute—while many tools can be defined behind them.
- •The framework compiles, validates, bundles, and serves standards-compliant MCP servers.
- •Built-in features include authentication, caching, and observability; no glue code required.
- •It reduces boilerplate compared to traditional MCP servers and supports prototypes to multi-agent production systems without architectural changes.