No user-submitted related servers found.
Scored across 95 tools
Most tools are clearly scoped by resource (dns, tunnel, kv, r2, zt, worker). However, there is notable overlap: cloudflare_zone_setting_get vs cloudflare_security_level_get (security_level is a zone setting), and cloudflare_security_insights vs cloudflare_security_insights_severity_count add nearly redundant tools. The WAF and IP access rule tools could also be confused.
All tools follow a consistent resource_noun_verb or resource_noun_action pattern (e.g., cloudflare_dns_list, cloudflare_r2_bucket_create). The naming clearly groups by service area and action, making it predictable across the large surface.
95 tools is extremely high for a coherent MCP server. While Cloudflare has many products, this set spans zones, DNS, WAF, tunnels, Zero Trust, Workers, KV, R2, analytics, and security — far too broad. An agent would struggle to discover and choose among 95 tools.
The core resources (DNS, KV, R2, Workers, Zero Trust, WAF) have solid lifecycle coverage — create/read/update/delete operations are present. Some gaps exist (no DNS bulk operations, no WAF ruleset update, no R2 object upload), but most workflows can be completed.