Full Supabase access: database, auth, storage, and edge functions.
- Home
- Top MCPs for Cloud & Infrastructure
- Cloudflare
Cloudflare
Reach the whole Cloudflare API from an agent — DNS records, Workers, R2, and the Registrar beta — through one hosted Code Mode server.
Quick answer
What it does
Exposes the Cloudflare REST API as a search-and-execute "Code Mode" pair rather than one tool per endpoint: the agent writes JavaScript against `spec.paths` to locate an endpoint, then calls it through `cloudflare.request()`. DNS record CRUD, zone settings, Workers deploys and rollbacks, R2 and KV, and the Registrar API's domain-search, domain-check and registrations endpoints are all reachable this way. The npm package `@cloudflare/mcp-server-cloudflare` is a different, older server: 89 Workers-platform tools, no DNS records, no Registrar, last published 2025-03-14.
Best for
- DNS record management on Cloudflare zones
- Worker deployment and rollback
- Domain search, check and registration via the Registrar API beta
- R2, KV and D1 operations
Not for
- Unattended DNS changes on production domains
- Domains held at another registrar
Source: top-mcps.com/mcp/cloudflare — verified Oct 2026
Setup recipe
Pick your client, then follow the three steps.
- 1
Install
claude_desktop_config.jsonjson{ "mcpServers": { "cloudflare": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.cloudflare.com/mcp" ] } } }Claude Desktop launches stdio servers, so mcp-remote bridges to the hosted endpoint and opens the sign-in in your browser. On Pro, Max, Team and Enterprise you can skip the file: Settings → Connectors → Add custom connector → https://mcp.cloudflare.com/mcp. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
CLI or .mcp.jsonshellclaude mcp add --transport http cloudflare https://mcp.cloudflare.com/mcpThen run /mcp inside Claude Code to finish the sign-in. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
.cursor/mcp.jsonjson{ "mcpServers": { "cloudflare": { "url": "https://mcp.cloudflare.com/mcp" } } }Global path: ~/.cursor/mcp.json. Cursor shows "Needs login" once it connects — click it to authorize. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
.vscode/mcp.jsonjsonc{ "servers": { "cloudflare": { "type": "http", "url": "https://mcp.cloudflare.com/mcp" } } }VS Code uses the "servers" key. Run MCP: List Servers → Start Server and allow the sign-in. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
~/.codeium/windsurf/mcp_config.jsonjson{ "mcpServers": { "cloudflare": { "serverUrl": "https://mcp.cloudflare.com/mcp" } } }Windsurf uses "serverUrl" for hosted servers. Open via Cascade → hammer icon → Configure. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
cline_mcp_settings.jsonjson{ "mcpServers": { "cloudflare": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.cloudflare.com/mcp" ] } } }Bridged through mcp-remote. Open via the Cline sidebar → MCP Servers → Edit. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
~/.continue/config.jsonjson{ "experimental": { "modelContextProtocolServers": [ { "transport": { "type": "streamable-http", "url": "https://mcp.cloudflare.com/mcp" } } ] } }Continue takes the hosted URL directly in the transport block. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
CLIshellcodex mcp add cloudflare --url https://mcp.cloudflare.com/mcpCodex detects OAuth support and opens the browser to authorize. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
~/.config/zed/settings.jsonjsonc{ "context_servers": { "cloudflare": { "command": { "path": "npx", "args": [ "-y", "mcp-remote", "https://mcp.cloudflare.com/mcp" ] } } } }Bridged through mcp-remote under "context_servers". Settings live-reload on save. Authorization happens in the browser on first use (OAuth); no token goes in the config file.
ChatGPT → Settings → Connectors (remote URL)json{ "name": "Cloudflare", "transport": "http", "url": "https://mcp.cloudflare.com/mcp" }Paste this into Settings → Connectors → Add custom connector. Requires ChatGPT Pro / Team / Enterprise / Edu with Developer mode enabled.
- 2
Set required secrets
No credentials required — this MCP runs over stdio without authentication.
- 3
Try a minimum working prompt
Audit deployed Workers
List every Worker deployed on my Cloudflare account with: name, last deployment date, and whether it has a custom route or just a workers.dev URL. Flag any that have not been deployed in over 180 days.Tested with: Claude Desktop, Cursor.
Tools & permissions
| Tool | Description | Args | Side effects |
|---|---|---|---|
search | Write JavaScript against the OpenAPI spec (`spec.paths`) to find the Cloudflare API endpoints for a task. | — | Read |
execute | Write JavaScript that calls the discovered endpoints through `cloudflare.request()` — reads and writes alike, with the credential's permissions. | — | Write |
docs | Search Cloudflare developer documentation. | — | Network |
Security & scope
- Access scope
- Read + write
- Sandbox
- OAuth lets you choose which permissions the connection gets; a bearer API token carries exactly its scopes. Whatever the credential allows, `execute` runs immediately — there is no confirmation layer in the server.
- Gotchas
- A credential with account-wide permissions hands the agent every zone, Worker and bucket. Create a scoped token — one zone, DNS edit only — for DNS work, and a separate one with Registrar write permission only when you intend to buy.
- Registrations through the Registrar API charge the account's default payment method and are non-refundable once complete. Put a human confirmation in front of any `execute` call that hits `/registrar/registrations`.
- API tokens with client IP address filtering enabled are not supported by the hosted server.
- The legacy `@cloudflare/mcp-server-cloudflare` npm package is not this server: 89 Workers-platform tools, no DNS records, no Registrar, and no release since 2025-03-14.
Agent prompt pack
— copy into Claude, Cursor, or ChatGPT.Recommend the best MCP servers for [task: e.g. cloud & infrastructure work] in [client: Claude]. Constraints: - Prefer tools that are [official | open-source | read-only] — pick what matters for my use case. - Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport]. - Return at most 3 picks, ranked. For each pick include: 1. One-sentence rationale. 2. The ready-to-paste install snippet for my client. 3. Any required secrets I need to create before installing. Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-cloud-infrastructure
Compare Cloudflare MCP vs [Vercel MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"]. Judge them on: - Setup time and complexity (what a new user hits first). - Auth model (none / API key / OAuth 2.1) and credential risk. - Transport (stdio / Streamable HTTP / SSE) and where the server runs. - Required secrets and the blast radius if they leak. - Operational risk in an unattended agent loop. - Which one is "good enough" for a weekend prototype vs. production. End with one sentence: which should I pick for my scenario, which is: [my scenario]. References: - https://top-mcps.com/mcp/cloudflare - top-mcps.com listing for Vercel
Install the Cloudflare MCP server for my [client: Claude] at the default config path for that client. Use the exact install snippet published at https://top-mcps.com/mcp/cloudflare (fetch https://top-mcps.com/mcp/cloudflare.json for the canonical server.json if you can read URLs). Before finishing: 1. Create the required secrets (no secrets) and put them in the appropriate env block — do not hard-code them. 2. Restart or reload the client so it picks up the new server. 3. Verify the server is connected (green / running state) and at least one tool is listed. 4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry. Confirm when done and list the tools the server now exposes.
Frequently asked questions
What changed
— 4 updates tracked.Cloudflare's published API spec now documents Registrar transfer-in, a transfer eligibility check and a registrar-sandbox path family; its Registrar API docs page (2026-09-16) still lists transfers as unavailable. The hosted endpoint answers 401 with OAuth as before.
Entry re-verified: the ranked path is the hosted Code Mode server at mcp.cloudflare.com/mcp (search, execute, docs). The npm package this entry used to install has no DNS or Registrar tools and was last published 2025-03-14.
containers-mcp@0.2.19, workers-observability@0.5.5 and dex-analysis@0.5.5 released in the servers monorepo
Cloudflare Registrar API beta announced: domain-search, domain-check and registrations endpoints, reachable through the Cloudflare MCP by default.
More Cloud & Infrastructure MCPs
Other tools in the same category worth evaluating.
Manage payments, customers, and subscriptions through Stripe.
Manage Droplets, App Platform, Kubernetes, and Spaces from an AI agent.
Compared with Cloudflare
Side-by-side breakdowns for the choices people most often weigh against this MCP.
Exploring Top MCPs for Cloud & Infrastructure? See all Cloud & Infrastructure MCPs →

