Side-by-Side Model Context Protocol Comparison
Cloud Tools vs Cloudflare MCP Pro
In-depth architectural comparison of the Cloud Tools and Cloudflare MCP Pro 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
Cloud Tools
Cloud Platforms · Local stdio
Quality: 61/100 (Good) | Auth: other
Cloudflare MCP Pro
Cloud Platforms · Local stdio
Quality: 60/100 (Good) | Auth: API Key required
Verdict Summary: Choose Cloud Tools if you need specialized Cloud Platforms tools running via a local process. Choose Cloudflare MCP Pro 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 Cloud Tools when:
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: other (Free / Open Source).
- You have access to required keys:
AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_PROFILE, GOOGLE_APPLICATION_CREDENTIALS, CLOUDFLARE_API_TOKEN, CLOUDFLARE_ACCOUNT_ID, OVH_APPLICATION_KEY, OVH_CONSUMER_KEY. - Primary tools included: compare_costs, get_commitments, get_costs.
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.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Cloud Tools Tools (7)
compare_costs
This period against the same day window of the previous month, so a partial month does not read as a fall. AWS and GCP only. GCP needs credentials.gcp.billing_table.
get_commitments
Commitments you are paying for, and whether you are consuming them, over the last 30 days. AWS: Savings Plans utilisation, coverage of eligible spend, and the saving a further commitment would give. GCP: committed use discounts with their expiry. Not implemented for Cloudflare or OVH, which sell no commitments.
get_costs
Cloud spend. AWS: by service over a date range, from Cost Explorer; pass group_by="data_transfer" for transfer cost by usage type. GCP: by service from the BigQuery billing export, which credentials.gcp.billing_table must name — without it you get budget amounts, not spend. Cloudflare: subscriptions and zone plan costs. OVH: the 6 most recent invoices.
get_cross_cloud_summary
One cost and waste report over every cloud you pass credentials for, with a grand total. Omit a cloud's credentials to skip it.
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).
Cloud Tools Configuration
Cloudflare MCP Pro Configuration