Cloudflare MCP Server
A token-efficient MCP server for the entire Cloudflare API. 2500 endpoints in 1k tokens, powered by Code Mode.
Token Comparison
| Approach | Tools | Token cost | Context used (200K) |
|---|
| Raw OpenAPI spec in prompt | — | ~2,000,000 | 977% |
| Native MCP (full schemas) | 2,594 | 1,170,523 | 585% |
| Native MCP (minimal — required params only) | 2,594 | 244,047 | 122% |
| Code mode | 3 | ~1,100 | 0.5% |
Get Started
MCP URL: https://mcp.cloudflare.com/mcp
Option 1: OAuth (Recommended)
Just connect to the MCP server URL - you'll be redirected to Cloudflare to authorize and select permissions.
Example JSON Configuration
{
"mcpServers": {
"cloudflare-api": {
"type": "http",
"url": "https://mcp.cloudflare.com/mcp"
}
}
}
Option 2: API Token
For CI/CD, automation, or if you prefer managing tokens yourself.
Create a Cloudflare API token with the permissions you need. Both user tokens and account tokens are supported. For account tokens, include the Account Resources : Read permission so the server can auto-detect your account ID.
Note: API tokens with Client IP Address Filtering enabled are not currently supported.
Add to Agent
Disable Code Mode
If your MCP client already uses code mode, or you're composing this server with another server that uses code mode, you can disable it with the ?codemode=false query parameter. This registers a tool for each Cloudflare API method instead of the code mode API tools, about 3,000, generated by forge. Each takes its arguments grouped by where they go: { path, query, headers, body }. The docs and whoami tools remain available in both modes.
https://mcp.cloudflare.com/mcp?codemode=false
Example JSON Configuration
{
"mcpServers": {
"cloudflare-api": {
"type": "http",
"url": "https://mcp.cloudflare.com/mcp?codemode=false"
}
}
}
When code mode is disabled:
- Each API endpoint is registered as its own tool (e.g.,
get_workers_scripts, post_d1_database)
- Tool input schemas are derived from the endpoint's path parameters, query parameters, and request body
- Tools make direct API calls — no code execution involved
- Path parameters like
account_id are auto-resolved when possible (single account)
Note: Disabling code mode significantly increases the token cost (~244k tokens vs ~1k tokens). Only disable it when necessary for composition with other code mode systems.
Tool Result Truncation
In code mode, the server caps each search and execute result at ~6,000 tokens, to avoid context overload. Oversized JSON stays valid JSON: long lists keep their first items whole, long strings are clipped, and every cut is marked with --- TRUNCATED ---. An agent that writes a result straight to a file or pipe, rather than reading it into the conversation, can pass truncate: false to that call to get the whole result.
Note: Without the cap, a broad query can return megabytes. Only turn it off when the result doesn't go to the model.
With code mode disabled, the direct tools return whole results. The clients that disable it usually run code mode themselves: they call the direct tools from their own code and parse each result, so a capped result would lose data.
Missing Permissions
When Cloudflare refuses a call because the OAuth connection lacks a scope, the server asks the client to re-authorize with that scope added to the ones it already has. Claude and other clients that follow the MCP authorization spec get a 403 insufficient_scope challenge. Codex and ChatGPT get it in the tool result, which is where they look for it. Either way, the tool error says which scope is missing. Some endpoints, such as GET /zones, don't refuse: they answer with an empty list when the scope is missing. An empty list from a read the connection holds no accepted scope for is refused the same way, so it isn't mistaken for an empty account.
The Problem
The Cloudflare OpenAPI spec is 2 million tokens. Even with native MCP tools using minimal schemas, it's still ~244k tokens. Traditional MCP servers that expose every endpoint as a tool leak this entire context to the main agent.
This server solves the problem by using code execution in a Code Mode pattern - the spec lives on the server, and only the result of the code execution is returned to the agent.
Tools
Agent writes code to search the spec and execute API calls. It can also search Cloudflare's developer documentation directly.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
