Skip to main content
📖 The AI Tool Bible

Cloudflare MCP Server vs MCP Everything Server

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

 Cloudflare MCP Server logo
Cloudflare MCP Server
MCP Servers
MCP Everything Server logo
MCP Everything Server
MCP Servers
TaglineOfficial suite of remote MCP servers that let Claude, Cursor, and other agents read and control your Cloudflare account.The kitchen-sink reference MCP server that exercises every corner of the Model Context Protocol
CategoryMCP ServersMCP Servers
PricingFreemium· Free: $0 USD · Team: $4 USD per user/month · Enterprise: $21 USD per user/monthFree· Free and open source (MIT License). No cloud service or paid tier — you run it locally via npx, Docker, or your MCP client of choice.
Model——
Editorial score——
Use cases
Debugging Workers with live logs from chatDeploying and configuring Workers bindingsGrounded Q&A over Cloudflare developer docsQuerying Radar for real-time internet traffic dataPulling audit logs for compliance answersRunning a headless browser via Browser RenderingAutoRAG pipelines against R2-hosted corporaReviewing Cloudflare One CASB findingsDNS analytics and Logpush inspectionBuilding custom MCP servers from the Demo Day template
MCP client conformance testingRegression testing of stdio and Streamable HTTP transportsVerifying sampling round-trip behavior in a new agent hostDebugging elicitation UI in an IDE integrationReference reading for authoring a new MCP serverDemoing MCP primitives in workshops and talksSmoke-testing cancellation and progress-notification handlingValidating resource-subscription update delivery
Pros
  • Official, first-party servers maintained by Cloudflare with 4k+ GitHub stars and active development.
  • Remote-hosted at stable URLs so most clients need only a URL and OAuth login, no local install.
  • Split into 16 focused servers so agents get relevant tools without prompt bloat.
  • Covers most of the Cloudflare platform: Workers, R2, KV, D1, Radar, DNS analytics, AI Gateway, AutoRAG, Browser Rendering, audit logs, CASB.
  • Works with any MCP-capable client - Claude Desktop, Claude Code, Cursor, Windsurf, and OpenAI Responses API.
  • Apache 2.0 source is on GitHub, so teams can self-host, audit, or extend any server.
  • Docs AI Search server gives agents grounded answers over the full developers.cloudflare.com corpus.
  • Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks
  • Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.)
  • Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports
  • TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped
  • MIT-licensed, no telemetry, no signup, no cloud dependency
  • Includes progress notifications and cancellation flows that most tutorial servers skip, so client cancel/timeout logic can be exercised properly
Cons
  • Only useful if you already run on Cloudflare - it is not a general cloud MCP.
  • Advanced capabilities inherit Cloudflare paywalls (Browser Rendering, AutoRAG, CASB, Cloudflare One all require paid plans).
  • Write-capable tools mean a compromised or over-permissioned token can push destructive changes; scoping API tokens carefully is on you.
  • Because the servers are hosted by Cloudflare, your agent's queries and returned data traverse Cloudflare infrastructure - not ideal for teams that want everything to stay in-VPC.
  • OAuth and remote-MCP support is still uneven across MCP clients, so setup varies and some clients need a manual token instead.
  • Sixteen separate endpoints can be confusing - discovery of which server owns which capability is not always obvious from client-side.
  • Explicitly not useful for end users — it does not do anything a human would actually want done
  • Feature drift means some primitives (SEP-1686 Tasks, elicitation) may not yet be implemented in every client, producing red herrings during testing
  • Documentation is a single features.md; there is no guided tour that maps each tool to the spec section it exercises
  • TypeScript-only reference — Python or Rust client authors have to translate patterns themselves
  • Sampling and elicitation flows depend on the client honoring them, so a silent client makes it hard to tell whether the server or the client is at fault
Websitegithub.comgithub.com
Pick Cloudflare MCP Server if
  • ✅ Official, first-party servers maintained by Cloudflare with 4k+ GitHub stars and active development.
  • ✅ Remote-hosted at stable URLs so most clients need only a URL and OAuth login, no local install.
  • ✅ Split into 16 focused servers so agents get relevant tools without prompt bloat.
  • ✅ Covers most of the Cloudflare platform: Workers, R2, KV, D1, Radar, DNS analytics, AI Gateway, AutoRAG, Browser Rendering, audit logs, CASB.
Pick MCP Everything Server if
  • ✅ Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks
  • ✅ Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.)
  • ✅ Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports
  • ✅ TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped
Compare a different pair →