In-depth architectural comparison of the Cloudflare MCP Pro and MCP Cloudflare DNS MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Cloudflare MCP Pro
Cloud Platforms · Local stdio
Quality: 60/100 (Good) | Auth: API Key required
MCP Cloudflare DNS
Cloud Platforms · Local stdio
Quality: 35/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Cloudflare MCP Pro if you need specialized Cloud Platforms tools running via a local process. Choose MCP Cloudflare DNS if your workspace requires Cloud Platforms integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Cloudflare MCP Pro when:
You need dedicated capabilities in the Cloud Platforms domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: CLOUDFLARE_API_TOKEN, CLOUDFLARE_ACCOUNT_ID, CLOUDFLARE_API_BASE.
Cloudflare MCP Pro is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, MCP Cloudflare DNS belongs to Cloud Platforms using local stdio subprocess. Select Cloudflare MCP Pro when you need capabilities focused on cloud platforms and MCP Cloudflare DNS when you require tools for cloud platforms.
The most complete Cloudflare MCP — 69 tools over the REST API v4 (DNS, Zones, Workers, KV, R2, D1, Pages, WAF, SSL, Email Routing, Logpush, Workers AI) in a single local stdio server, with a server-side human-approval gate on every mutation. npx -y cloudflare-mcp-pro.
Cloudflare DNS MCP server: manage zones, records, cache purge, and page rules.