Cloudflare's Two-Tool MCP Pattern Cuts 1.17M Tokens to 1,000

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 definitions. Their solution uses exactly two tools: search() and execute(). Total token footprint: roughly 1,000. That's a 99.9% reduction.

Here's how it works. The search() tool lets an agent query the OpenAPI spec by product area without loading the entire spec into context. The agent finds the endpoints it needs. Then execute() runs agent-generated JavaScript inside a V8 isolate, handling pagination and chained API calls in a single cycle. The agent writes code against a TypeScript API rather than making sequential tool calls.

The key insight, and this is the part I want every builder to internalize: converting MCP tool definitions into a typed API and asking the LLM to write code against it consistently outperforms sequential tool calling. Cloudflare's benchmarks show 81-99.9% token reduction depending on the API surface.

I've been struggling with this exact problem. I have a FastAPI backend with 120+ endpoints, and exposing them all via MCP is absurd. The context window fills up with tool schemas before the agent even starts thinking about your actual request. Cloudflare just showed us the pattern: search over the spec, execute code against a typed SDK.

This approach is portable to any API with an OpenAPI spec. You don't need Cloudflare's infrastructure. Generate a TypeScript client from your spec, expose search and execute as MCP tools, and let the agent write code. I'm planning to try this on my own API this week.

The 99.9% token reduction also matters for cost. If you're running agents that interact with large APIs, your token bills are dominated by tool definitions the agent may never use. Two tools that dynamically discover what's available fixes the economics.