Cloudflare MCP Server vs MCP Fetch Server

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

	Cloudflare MCP Server MCP Servers	MCP Fetch Server MCP Servers
Tagline	Official suite of remote MCP servers that let Claude, Cursor, and other agents read and control your Cloudflare account.	Official Model Context Protocol reference server that lets any MCP-compatible LLM fetch web pages and read them as clean markdown.
Category	MCP Servers	MCP Servers
Pricing	Freemium· Free: $0 USD · Team: $4 USD per user/month · Enterprise: $21 USD per user/month	Free· Free and open source (MIT License). No hosted tier; you run it locally via uvx, pip, or Docker.
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	Reading documentation pages inside Claude DesktopGrabbing a GitHub README before scaffolding a projectSummarising a long article for a chat agentChecking a package changelog during code reviewAnswering questions from a linked spec section by sectionFeeding a URL into an MCP-driven research agentPulling clean markdown for a note-taking workflowVerifying a citation URL inside an editorial pipeline
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.	Official reference implementation maintained in the modelcontextprotocol/servers repo — tracks the spec and won't rot behind third-party churn. Zero-install path via `uvx mcp-server-fetch`; Docker image and pip package also available for sandboxed or reproducible setups. HTML-to-markdown conversion produces context-window-friendly output instead of raw tag soup. `max_length` + `start_index` let a model chunk through long pages without blowing its context. Optional Node.js fallback swaps in a more robust HTML simplifier when present. First-class configuration for User-Agent, robots.txt obedience, and outbound proxy — practical knobs for real-world scraping etiquette. Works out of the box with every major MCP client (Claude Desktop, Claude Code, VS Code, Cursor, Zed, Continue).
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.	No JavaScript rendering — SPAs, Cloudflare-challenged pages, and content loaded after DOMContentLoaded come back empty or as a shell. No built-in anti-bot handling; sites that block plain HTTP clients (many news sites, LinkedIn, X) will 403. Security caveat called out in the README: the server can reach local/internal IPs, so it is a genuine SSRF risk if exposed to an untrusted model or user. Single tool, single verb — for crawling, sitemap walks, or extracting structured data you need a heavier server like Firecrawl-MCP or a Playwright-based one. Truncation defaults to 5,000 characters; models that don't understand `start_index` can silently miss content below the fold.
Website	github.com	github.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 Fetch Server if

✅ Official reference implementation maintained in the modelcontextprotocol/servers repo — tracks the spec and won't rot behind third-party churn.
✅ Zero-install path via `uvx mcp-server-fetch`; Docker image and pip package also available for sandboxed or reproducible setups.
✅ HTML-to-markdown conversion produces context-window-friendly output instead of raw tag soup.
✅ `max_length` + `start_index` let a model chunk through long pages without blowing its context.

Compare a different pair →