Search and execute API access
Expose more than 2,500 Cloudflare endpoints through search() and execute() while keeping schema context compact.
Documentation ↗MCP server / cloud & infrastructure / source-linked
Cloudflare MCP
Cloudflare’s managed MCP catalog includes an API server for DNS, Workers, R2, Zero Trust, and other products. The current API MCP uses Streamable HTTP and a search-and-execute Code Mode pattern: two tools operate over a typed API representation instead of loading thousands of endpoint schemas into the model context. OAuth is interactive; API tokens support automation.
Before you choose.
Identify the implementation and the job it supports.
Cloudflare’s managed MCP catalog includes an API server for DNS, Workers, R2, Zero Trust, and other products. The current API MCP uses Streamable HTTP and a search-and-execute Code Mode pattern: two tools operate over a typed API representation instead of loading thousands of endpoint schemas into the model context. OAuth is interactive; API tokens support automation.
Setup and connection.
The documented interface, authentication and installation path.
- Connection / transport
- Streamable HTTP at https://mcp.cloudflare.com/mcp
- Authentication
- OAuth for interactive clients; Cloudflare API token bearer auth for CI/CD.
Add the official URL to the MCP client, complete Cloudflare OAuth, and select account permissions. For automation, create a least-privilege API token and pass it as Authorization.
Setup reference ↗Documented setup example. Review the source and credentials before running; this command was not executed for this article.
{"mcpServers":{"cloudflare-api":{"url":"https://mcp.cloudflare.com/mcp"}}}What it actually exposes.
Concrete capabilities with maintainer sources.
Cross-product operations
Cover DNS, Workers, R2, Zero Trust, and other Cloudflare account services through the API server.
Documentation ↗Managed server catalog
Cloudflare also operates domain-specific managed MCP servers for application development, security, and performance workflows.
Documentation ↗Evidence and method.
What was checked and what was not tested.
HOW
Source method
Public maintainer documentation and repositories. This is not a hands-on product review.
WHEN
Last checked 2026-10-01
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
Community signals.
Concrete reports from public community discussions, kept separate from product documentation.
Cloudflare's new MCP setup is pretty interesting
The thread highlights Cloudflare Code Mode's catalog-plus-executor design as a response to large tool schemas, while questioning endpoint discovery accuracy.
“Cloudflare reduced roughly 244K tokens of endpoint definitions to about 1.1K using a catalog and generic executor.”Open community source ↗
PSA: MCP servers hanging on Cloudflare Workers? Use createMcpHandler
A developer found the Workers runtime required Cloudflare's wrapper instead of the raw web-standard transport to avoid hanging MCP requests.
“Using the raw SDK transport made Workers hang; Cloudflare's createMcpHandler wrapper fixed connection lifecycle and streaming.”Open community source ↗
Community evidence is anecdotal and may reflect one setup, version or account. It is included for discovery and risk-sensing, not as a representative rating or independent benchmark. Verify the current official documentation before acting on a report.
Try a specific task.
A bounded evaluation you can reproduce in your own environment.
Edge change review
Suggested evaluation, not an observed test result.
- Connect OAuth to a sandbox account or a token scoped to one zone/service.
- Ask the agent to search the API for the current configuration and produce a diff.
- Review generated execute code and approve one reversible change at a time.
What to inspect: A small, reviewable edge configuration diff instead of a blind command sequence. Proposed workflow; not tested by clawbot.ai.
Workflow reference ↗Permissions and limitations.
Read these constraints before granting access.
Code Mode reduces tool-schema context but shifts safety to generated code and API permissions; this is an inference from the documented search/execute architecture.
Boundary reference ↗An API token can grant broad account access; scope it to the exact zone/account actions needed.
Boundary reference ↗Decide by workflow.
Make the expected output explicit before you connect.
A small, reviewable edge configuration diff instead of a blind command sequence. Proposed workflow; not tested by clawbot.ai.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Compare the alternatives.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| Vercel MCP | Choose for Vercel project/deployment operations. | Vercel is app-platform focused; Cloudflare spans edge, DNS, security, and storage. Documentation ↗ |
| Docker MCP Toolkit | Choose when the main problem is local server packaging and isolation. | Docker governs MCP runtimes; Cloudflare governs production edge resources. Documentation ↗ |
Questions before setup.
Answers specific to this implementation.
Why only two tools for thousands of APIs?
Cloudflare uses search-and-execute Code Mode to keep the model context near 1,000 tokens instead of loading every endpoint schema.
Documentation ↗
Can CI use OAuth?
The docs describe API-token bearer auth for CI/CD; OAuth is the interactive client path.
Documentation ↗
Source trail.
Maintainer documentation used in this record.