Cloudflare MCP Server

Overview

The Cloudflare MCP Server gives AI agents access to the entire Cloudflare API — roughly 2,500 endpoints — through the Model Context Protocol, while using only about 1,000 tokens of context. It achieves this with Cloudflare’s “Code Mode” pattern: instead of exposing every endpoint as a separate tool, the agent writes small pieces of code that search the API spec and execute calls on the server.

Why Code Mode Matters

The full Cloudflare OpenAPI spec is about 2 million tokens. Even a minimal MCP tool per endpoint costs around 244,000 tokens — more than most context windows. Code Mode keeps the spec on the server and returns only the results, so the agent’s context stays small.

Tools

Getting Started

Add the hosted server to any MCP-compatible client:

{
  "mcpServers": {
    "cloudflare-api": {
      "type": "http",
      "url": "https://mcp.cloudflare.com/mcp"
    }
  }
}

• OAuth (recommended): connect and you are redirected to Cloudflare to authorize and choose permissions.
• API token: for CI/CD and automation, pass a Cloudflare API token as a bearer token (user and account tokens are both supported).

Options

• ?codemode=false registers one tool per endpoint, for clients that already implement Code Mode themselves (much higher token cost).
• ?truncateToolResult=false disables the default ~6,000-token cap on each tool result, for clients that bound results on their own.

Use Cases

• Let a coding agent configure DNS, Workers, R2, or WAF rules in plain language
• Automate account audits and reporting across many zones
• Combine Cloudflare operations with other MCP servers in one agent

License

Apache License 2.0.