A
licenseNot graded
qualityC
maintenanceAn MCP server that allows using natural language to manage Cloudflare resources (Workers, KV, R2, D1) through Claude Desktop, VSCode, and other MCP clients.
16 npm
10
Apache 2.0
cloudflare-mcp
by pocc
Related Servers
Alternatives to cloudflare-mcp
No user-submitted related servers found.
Related Servers
Cloudflare MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceA token-efficient MCP server that provides access to the entire Cloudflare API (2500+ endpoints) using a code execution pattern, enabling natural language management of Cloudflare services.5 npm824Apache 2.0mcp-server-cloudflareofficial
AlicenseAqualityAmaintenanceLets you use Claude Desktop, or any MCP Client, to use natural language to accomplish things on your Cloudflare account.21,282 npm4,183Apache 2.0- AlicenseAqualityBmaintenanceCloudflare DNS MCP server. Manage zones, DNS records, cache, and page rules from Claude, Cursor, Codex, or any MCP-compatible AI assistant.10MIT
- AlicenseNot gradedqualityNot gradedmaintenanceA lightweight MCP server for managing DNS records, purging cache, and interacting with the Cloudflare API through natural language commands.24-
- AlicenseNot gradedqualityCmaintenanceCloudflare MCP server with multi-user credential management, full Cloudflare API coverage, and schema discovery tools for safe LLM-driven Cloudflare resource management.5 npmMIT
TDQS
C2.4/5.0
Scored across 390 tools
Disambiguation2/5
With 390 tools, many resource families are nearly indistinguishable from an agent's perspective, such as list_workers vs list_worker_services, list_api_shield_operations vs list_api_gateway_operations, and get_zone_setting vs get_zone_settings. The descriptions help, but the scale and overlapping naming create substantial misselection risk.
Naming Consistency3/5
The dominant pattern is list_<plural> and get_<singular>, which is readable, but there are many deviations: collection-style get_*_rules/get_*_settings use 'get' instead of 'list', and tools like graphql_analytics, get_analytics_by_colo, and verify_token break the pattern. Overall the naming is mostly predictable but not consistently applied.
Tool Count1/5
390 tools is an extreme number for an agent-facing MCP server, far beyond the 50+ threshold. Even if Cloudflare's API is broad, exposing nearly every read-only endpoint as a separate tool makes the interface overwhelming and hard to navigate efficiently.
Completeness1/5
The entire tool surface is read-only: every tool is get/list/query style, with no create, update, or delete operations for any resource. A general Cloudflare management server cannot complete common workflows like creating DNS records or updating rules, making the set severely incomplete for its implied purpose.
Maintenance
ActivityInactive
ResponsivenessNo issues