Cloudflare MCP Server vs Puppeteer MCP Server

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

	Cloudflare MCP Server MCP Servers	Puppeteer MCP Server MCP Servers
Tagline	Official suite of remote MCP servers that let Claude, Cursor, and other agents read and control your Cloudflare account.	Reference MCP server that lets LLMs drive a real Chromium browser via Puppeteer.
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 service; you run it locally under Node/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	Give Claude a browser to research JS-rendered pagesHave an agent fill and submit a web formTake element-scoped screenshots for bug reportsSmoke-test a local staging site from an LLMScrape specific fields the model identifies visuallyAutomate a signed-in web workflow via headful loginExtract data with in-page JS via puppeteer_evaluatePrototype a custom browser-MCP by forking the reference
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.	Zero-config bridge between any MCP client and a real Chromium instance, including JS-heavy SPAs that curl or fetch-based tools cannot see. Complete open-source TypeScript reference implementation, easy to fork as a starting point for a hardened production browser-MCP. Ships both NPX (headful, interactive login friendly) and Docker (headless, sandboxed) install paths. Screenshots are exposed as MCP resources with stable names, so a model can refer back to earlier captures across a conversation. puppeteer_evaluate gives the model an escape hatch to run arbitrary in-page JS when the fixed click/fill/select tool set is not enough. Console log resource lets the agent read runtime errors without a separate devtools bridge.
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.	Archived on 29 May 2025 (read-only) and no longer maintained by Anthropic; expect Puppeteer/Chromium drift over time. Runs a browser on your machine with access to local files and localhost/private IPs, which is a real prompt-injection and SSRF risk if the model visits hostile pages. No built-in proxy rotation, stealth patches, CAPTCHA handling, or Cloudflare-turnstile bypass, so it is not suitable for anti-bot-hardened targets. Selector-based tools rely on the model producing correct CSS selectors; brittle on frequently-changing DOMs. No session persistence, cookie import, or multi-tab management primitives out of the box. Community forks (Playwright MCP, browserless MCP, hyperbrowser, etc.) have moved past this reference in features and active support.
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 Puppeteer MCP Server if

✅ Zero-config bridge between any MCP client and a real Chromium instance, including JS-heavy SPAs that curl or fetch-based tools cannot see.
✅ Complete open-source TypeScript reference implementation, easy to fork as a starting point for a hardened production browser-MCP.
✅ Ships both NPX (headful, interactive login friendly) and Docker (headless, sandboxed) install paths.
✅ Screenshots are exposed as MCP resources with stable names, so a model can refer back to earlier captures across a conversation.

Compare a different pair →