Cloudflare MCP Pro vs Infrawise — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Cloudflare MCP Pro vs Infrawise
In-depth architectural comparison of the Cloudflare MCP Pro and Infrawise 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
Infrawise
Cloud Platforms · Local stdio
Quality: 64/100 (Good) | Auth: API Key required
Verdict Summary: Choose Cloudflare MCP Pro if you need specialized Cloud Platforms tools running via a local process. Choose Infrawise 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.
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.
Cloud infrastructure analysis for AI coding assistants — detects IaC drift, missing indexes, security gaps, and performance anti-patterns across AWS services and databases. 13 tools, works with Claude Code and Cursor.
Category & Scope
Tools & Capabilities Breakdown
Cloudflare MCP Pro Tools (69)
verify_token
Validate the configured Cloudflare API token and show its status/permissions.
list_accounts
List Cloudflare accounts accessible by the token.
list_zones
List zones (domains), optionally filtered by name or status.
get_zone
Get details of a single zone by ID.
create_zone
Add a new domain (zone) to an account. Requires confirm:true (human-approval gate); without it returns a preview only.
delete_zone
Delete a zone by ID. Requires confirm:true (human-approval gate); without it returns a preview only.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Cloudflare MCP Pro is categorized under Cloud Platforms and uses a local stdio subprocess. In contrast, Infrawise belongs to Cloud Platforms using local stdio subprocess. Select Cloudflare MCP Pro when you need capabilities focused on cloud platforms and Infrawise when you require tools for cloud platforms.
Purge a zone's cache — everything, or by files/tags/hosts/prefixes. Requires confirm:true (human-approval gate); without it returns a preview only.
get_zone_analytics
Get HTTP traffic analytics for a zone over a time range (via GraphQL).
get_zone_setting
Get a single zone setting (e.g. ssl, always_use_https, min_tls_version).
update_zone_setting
Update a single zone setting (e.g. set ssl=full, always_use_https=on). Requires confirm:true (human-approval gate); without it returns a preview only.
list_dns_records
List DNS records of a zone, optionally filtered by type/name.
create_dns_record
Create a DNS record (A, AAAA, CNAME, TXT, MX, etc). Requires confirm:true (human-approval gate); without it returns a preview only.
+57 more tools listed on main page
Infrawise Tools (22)
get_infra_overview
Complete snapshot — services, counts, high-severity findings, `configured` flag (data age and per-source status ride the `dataHealth` block on every response)
get_graph_summary
Full infrastructure graph — all nodes, edges, and findings
get_table_schema
Column-level schema for named tables/collections — types, PKs, FKs, indexes, DynamoDB keys/billing mode, cost signal (no row data)
analyze_function
Issues in a specific function — scans, missing indexes, N+1, trigger event shapes, missing IAM permissions; returns every same-named file as a separate match, or bind to one with the optional `file` input; names refused Lambda links and why (`unresolvedLambdas`)
suggest_gsi
Exact GSI config for a DynamoDB table + attribute — names the existing index instead when one already covers it
postgres_index_suggestions
Exact `CREATE INDEX` SQL for your actual table
suggest_mongo_index
Exact `createIndex` command for a MongoDB collection + field
mysql_index_suggestions
Exact `ALTER TABLE ADD INDEX` SQL for your MySQL table