Fetching from the wire…
Public story · 2026-08-23 · high
The project credits Cloudflare's Code Mode portal as the pattern it's copying, and skips publishing any pricing.
Why now: OneMCP posted to Show HN on August 23.
OneMCP showed up on Hacker News on August 23 with a portal that replaces dozens of MCP tool definitions with three commands. Point it at your existing servers, 20-plus in the example given, and it exposes only search, describe and execute.
The stakes are cost and speed. Every MCP server wired into an agent adds tokens to its system prompt before a single request happens, and OneMCP claims the three-tool portal cuts that prompt by about 90%.
The mechanics matter more than the headline number. Instead of a model reading every tool's full schema on each call, it searches for what it needs, gets a description, then executes it. That's closer to writing code against an API than loading a full reference sheet into context every turn. OneMCP names Cloudflare's Code Mode portal as the pattern it's built on.
There's no pricing on the page. It's also a single source, so treat the 90% figure as OneMCP's own claim until someone benchmarks it.
Here's the tension worth watching. OneMCP is solving a problem that shouldn't need solving forever. MCP's own roadmap includes progressive discovery work aimed at the same context bloat, built into the protocol instead of wrapped around existing servers. If that ships and gets adopted, tools like OneMCP either fold into the spec or become redundant middleware.
Each link below shares sources, entities, or timing with this story.
Cloudflare published Code Mode for MCP, and the numbers are the kind that change how you architect things. Instead of exposing MCP tools individually to an LLM (each tool call requires a round trip through the model), Code Mode converts your entire MCP server into a typed Type...
This is the most immediately useful pattern I've seen this month. Cloudflare shipped Code Mode MCP, and the numbers are hard to argue with. Their API has 2,500+ endpoints. Exposing each one as a separate MCP tool would consume 1.17 million tokens of context just for tool defin...
Cloudflare shipped Code Mode MCP this week, and the numbers are hard to ignore. They replaced per-endpoint tool definitions with exactly two tools: search() and execute(). That's it. The result? Their own API surface, all 2,500+ endpoints, went from 1.17 million tokens of tool...
Buried at 4 points on Show HN, which is a shame, because it's the most consequential idea in today's Show HN cluster. Every MCP server you connect burns context on tool schemas before the agent does any work, and aggregation behind a two-tool facade is the obvious fix nobody h...
PR #29081, merged August 26 and in nightly v0.59.0-nightly.20260827, enforces RFC 9728 §7.7 and RFC 8414 constraints across MCP OAuth metadata discovery, dynamic client registration, and token exchange. It requires HTTPS for remote endpoints with HTTP allowed only for loopback...
v4.1.16, also August 26, hides them because "the per-tool checkboxes were no-ops that implied granularity the approval path does not have." MCP auto-approval is governed entirely by the global "Use MCP servers" toggle. Anyone who ticked auto-approve for a read-only tool while...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.