2,594 Tools Down to 2: Cloudflare's Code Mode Migration Checklist After Retiring the Vectorize-Backed AutoRAG MCP Server

Why the Dedicated RAG MCP Server Went Away

Since early 2026, Cloudflare has moved ten product-specific MCP servers — AutoRAG, AI Gateway, Audit Logs, DNS Analytics, GraphQL, Logpush, Observability, Radar, Workers Bindings, and Workers Builds — into the "Deprecated" section of its official repo (cloudflare/mcp-server-cloudflare). AutoRAG was the dedicated server that answered RAG queries by searching a Vectorize index, exposing purpose-built tools like list_rags and ai_search. The deprecation notice only says to "migrate at your earliest convenience" — no sunset date is given.

The replacement is a single unified server at mcp.cloudflare.com/mcp. It exposes the entire Cloudflare API, Vectorize included, through code execution, so the same RAG queries run without a dedicated tool. What disappears is the type-safe calling experience a purpose-built tool gave you — the model now has to walk the OpenAPI spec itself, in code.

The Math Behind Collapsing 2,594 Tools into Two

Expose the full schema natively and the unified server's 2,594 endpoints cost 1,170,523 tokens — 585% of a 200K context window. Trimming to required parameters only still costs 244,047 tokens (122%). Code Mode, which collapses everything into four tools (search, execute, docs, whoami), uses about 1,100 tokens — 0.5%.

The search tool walks the OpenAPI spec (spec.paths) in code to find endpoints; execute calls cloudflare.request() to run the actual API. The spec itself stays server-side and only the code's result comes back to the model, so the token footprint stays fixed no matter how many endpoints exist. The generated code runs inside an isolated Worker via the Dynamic Worker Loader API.

Four Things to Lock Down Before You Migrate

Declare a token budget in numbers before migrating: target context usage at 1% or under (0.5% with Code Mode), restrict the native-mode fallback (?codemode=false) to emergency debugging only, and decide in advance which calls need truncate: false — results are capped at roughly 6,000 tokens by default, so only calls that genuinely need bulk output should override it.

Four failure patterns show up in practice. Leave the old call pattern in place after the notice lands, and the native schema's 1,170,523-token cost pushes context usage to 585%. Leave the ten deprecated server URLs unmonitored, and connections cut out abruptly behind a notice with no sunset date. An API token with Client IP Address Filtering enabled silently fails auth on the unified server. An account token missing Account Resources:Read permission gets its execute calls rejected outright.

Build two recovery branches: switch to the OAuth path immediately on an auth failure to sidestep token-scope issues, and retry with truncate disabled whenever a response gets cut off at the cap.

The operations checklist needs four fields logged on every call — tool_count, context_pct, the truncate setting, and the auth method — plus a quarterly sweep of all ten deprecated server endpoints to track which ones still resolve. Right after migrating, run ?codemode=false and the default mode side by side for a week to confirm there's no regression.

The improvement loop starts with tracking how the vendor phrases its deprecation notices. When "migrate at your earliest convenience" keeps showing up with no sunset date, set an internal recheck cadence — monthly is reasonable — so your team closes the gap between the notice and the actual cutoff instead of the vendor.

Takeaways at a Glance

Cloudflare's decision to fold ten product-specific MCP servers, AutoRAG and its Vectorize backing among them, into a search/execute-centered Code Mode server moved the baseline for tool design from type safety to token budget. Put a number on the migration target — context usage under 1% — and bake the three failure points (auth failures, response caps, sunset-dateless deprecation notices) into a checklist, and the same procedure holds for whatever Cloudflare consolidates next.

References

Cloudflare API MCP Server — cloudflare/mcp

Cloudflare MCP Servers (product-specific, deprecated list) — cloudflare/mcp-server-cloudflare