cloudflare-mcp-pro
Related Servers
Alternatives to cloudflare-mcp-pro
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceSlim Cloudflare MCP Server — 42 tools for managing DNS, zones, tunnels, WAF, Zero Trust, and security via Cloudflare API v4. Multi-zone support. No SSH, no shell, API-only with 3 runtime dependencies. AGPL-3.0 + Commercial dual-licensed.9665 npmAGPL 3.0
- AlicenseNot gradedqualityNot gradedmaintenanceA token-efficient MCP server for managing Cloudflare DNS zones and records with full CRUD support and bulk operations. It can be deployed locally via stdio or as a Cloudflare Worker for remote HTTP access.-
- AlicenseAqualityBmaintenanceCloudflare DNS MCP server. Manage zones, DNS records, cache, and page rules from Claude, Cursor, Codex, or any MCP-compatible AI assistant.10MIT
- AlicenseAqualityDmaintenanceMCP server to manage Cloudflare Workers, KV, R2, Pages, DNS, and cache from your IDE.1336 npm4MIT
- AlicenseNot gradedqualityCmaintenanceProvides a unified MCP interface to manage Cloudflare services including DNS, compute (Workers, KV, D1), storage (R2), AI, security, Radar, and a universal API gateway for any Cloudflare v4 endpoint.MIT
- AlicenseNot gradedqualityCmaintenanceCloudflare MCP server with multi-user credential management, full Cloudflare API coverage, and schema discovery tools for safe LLM-driven Cloudflare resource management.7 npmMIT
TDQS
Scored across 69 tools
Most tools target distinct Cloudflare resources (DNS, Workers, KV, D1, etc.), and descriptions clearly differentiate them. A few pairs like 'get_zone' and 'get_zone_setting' could cause minor confusion, but overall boundaries are clear.
The majority follow a verb_noun pattern (e.g., create_dns_record), but there are deviations like 'kv_get', 'deploy_worker', 'edit_dnssec', and 'verify_token'. The mixture of conventions reduces predictability.
69 tools is excessively high for a single MCP server, leading to context overload. The broad scope would be better served by splitting into multiple specialized servers (e.g., DNS, Workers, Storage).
The tool surface covers core CRUD for many services (DNS, Workers KV, Zones) but lacks update operations for custom hostnames, D1 databases, R2 buckets, and queues. Additionally, firewall rules and SSL certificate management are incomplete.