CLOUD OPERATIONS / Cloudflare
Cloudflare API MCP
Lets an assistant discover Cloudflare API endpoints and execute API calls through code, within the granted Cloudflare permissions.
“MCP server for the entire Cloudflare API using codemode”
01 / THE REASONING
Why this made the selection.
- API discovery and execution share one source-backed workflow, including documentation lookup.
- OAuth and API-token paths allow interactive and automated deployments with explicit Cloudflare grants.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- README.md (installation, tools, code-mode, truncation and skills sections)
- package.json
- src/index.ts
- LICENSE
- src/mcp-handler.ts
Our findings
- The entrypoint wraps the MCP handler in an OAuth provider and also supports externally supplied Cloudflare credentials.
- The documented execute tool runs JavaScript that calls cloudflare.request; account/token rights are the relevant authority boundary.
- The README at this commit lists four tools: docs, search, execute and whoami. With ?codemode=false the server instead registers one tool per API endpoint that makes direct API calls; docs and whoami remain.
- The README says generated code runs in isolated Workers through Cloudflare’s Dynamic Worker Loader API, so execute runs on Cloudflare’s side, not on the client machine.
- src/index.ts configures an OAuth provider with authorize, token and client-registration endpoints, and delegates directly supplied Cloudflare API tokens to resolveExternalToken. A comment there says the consent page offers further scopes read-only by default.
- The README says the server also serves Cloudflare skills through the MCP Skills extension, synced from GitHub.
Not established by this review
- Server startup, authentication and tool execution were not tested.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
- Add the documented remote configuration and complete Cloudflare OAuth.
- Select only the necessary account permissions; use the API-token path only with a suitably scoped token.
Before you start
- A Cloudflare account and a remote-capable MCP client.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"cloudflare-api": {
"type": "http",
"url": "https://mcp.cloudflare.com/mcp"
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- Official documentation ↗Checked
https://github.com/cloudflare/mcp/blob/e85737947299bbb9b5858fc9ae6bc6d1e6f9a3ba/README.md
Supports: summary, whySelected, bestFor, limitations, install, access, compatibility, transports, configExample, Tool list: docs, search, execute, whoami, OAuth and API-token authentication, Result truncation cap, Skills extension
- Applicable source licence ↗Checked
https://github.com/cloudflare/mcp/blob/e85737947299bbb9b5858fc9ae6bc6d1e6f9a3ba/LICENSE
Supports: license
https://github.com/cloudflare/mcp/blob/e85737947299bbb9b5858fc9ae6bc6d1e6f9a3ba/package.json
Supports: language, review
https://github.com/cloudflare/mcp/blob/e85737947299bbb9b5858fc9ae6bc6d1e6f9a3ba/src/index.ts
Supports: language, review, OAuth provider and resolveExternalToken, Consent scopes read-only by default (code comment)
https://github.com/cloudflare/mcp/blob/e85737947299bbb9b5858fc9ae6bc6d1e6f9a3ba/src/mcp-handler.ts
Supports: review, transports