Which API token permissions does it need?

The minimum depends on what you want the agent to do. For read-only: `Account Analytics:Read`, `Zone:Read`. For Workers deploys add `Workers Scripts:Edit`. Create scoped tokens per use case rather than using the global key.

Can it deploy Workers from source?

Yes. The MCP can publish a Worker from either inline code or a bundle path, set env vars and bindings (KV, R2, D1), and roll back to a previous version if the deploy fails.

Is this safe to run against production DNS?

Only with approval turned on and a scoped token. DNS mistakes propagate quickly and can black-hole traffic. Pair it with Cloudflare's Change History so every agent-initiated change is auditable.

Does it support the Zero Trust / Access APIs?

Yes for the most common endpoints (Access applications, policies, users). Some newer Zero Trust features land on the REST API first and in the MCP shortly after — check the release notes for coverage.

Cloudflare

Name: Top MCPs — curated MCP directory
Creator: Top MCPs
License: https://creativecommons.org/licenses/by/4.0/

Official

Manage Workers, R2 buckets, DNS, and edge policies on Cloudflare.

Score 82(?)CloudflareApache-2.0 3.6kVerified May 28, 2026Top MCPs for Cloud & Infrastructure →

Install View on GitHub

Quick answer

What it does

Surfaces Cloudflare's REST API for Workers, R2, KV, DNS, WAF, and analytics as MCP tools that agents can invoke.

Best for

Worker deployment
DNS record management
R2 bucket operations
WAF rule updates

Not for

Unattended DNS changes on production domains
Compliance-audited infra flows without approval

Setup recipe

Pick your client, then follow the three steps.

Install

claude_desktop_config.jsonjson

{
  "mcpServers": {
    "cloudflare": {
      "command": "npx",
      "args": [
        "-y",
        "@cloudflare/mcp-server-cloudflare"
      ],
      "env": {
        "CLOUDFLARE_API_TOKEN": "${CLOUDFLARE_API_TOKEN}",
        "CLOUDFLARE_ACCOUNT_ID": "${CLOUDFLARE_ACCOUNT_ID}"
      }
    }
  }
}

Paste under mcpServers. Fully quit and reopen Claude after editing.

CLI or .mcp.jsonshell

# export CLOUDFLARE_API_TOKEN=your_scoped_token
# export CLOUDFLARE_ACCOUNT_ID=your_account_id
claude mcp add cloudflare -- npx -y @cloudflare/mcp-server-cloudflare

Run from your repo. Commit .mcp.json to share with your team.

.cursor/mcp.jsonjson

{
  "mcpServers": {
    "cloudflare": {
      "command": "npx",
      "args": [
        "-y",
        "@cloudflare/mcp-server-cloudflare"
      ],
      "env": {
        "CLOUDFLARE_API_TOKEN": "${CLOUDFLARE_API_TOKEN}",
        "CLOUDFLARE_ACCOUNT_ID": "${CLOUDFLARE_ACCOUNT_ID}"
      }
    }
  }
}

Global path: ~/.cursor/mcp.json. Reload window after editing.

.vscode/mcp.jsonjsonc

{
  "servers": {
    "cloudflare": {
      "command": "npx",
      "args": [
        "-y",
        "@cloudflare/mcp-server-cloudflare"
      ],
      "env": {
        "CLOUDFLARE_API_TOKEN": "${CLOUDFLARE_API_TOKEN}",
        "CLOUDFLARE_ACCOUNT_ID": "${CLOUDFLARE_ACCOUNT_ID}"
      }
    }
  }
}

VS Code uses the "servers" key (not "mcpServers").

~/.codeium/windsurf/mcp_config.jsonjson

{
  "mcpServers": {
    "cloudflare": {
      "command": "npx",
      "args": [
        "-y",
        "@cloudflare/mcp-server-cloudflare"
      ],
      "env": {
        "CLOUDFLARE_API_TOKEN": "${CLOUDFLARE_API_TOKEN}",
        "CLOUDFLARE_ACCOUNT_ID": "${CLOUDFLARE_ACCOUNT_ID}"
      }
    }
  }
}

Open via Cascade → hammer icon → Configure.

cline_mcp_settings.jsonjson

{
  "mcpServers": {
    "cloudflare": {
      "command": "npx",
      "args": [
        "-y",
        "@cloudflare/mcp-server-cloudflare"
      ],
      "env": {
        "CLOUDFLARE_API_TOKEN": "${CLOUDFLARE_API_TOKEN}",
        "CLOUDFLARE_ACCOUNT_ID": "${CLOUDFLARE_ACCOUNT_ID}"
      }
    }
  }
}

Open via the Cline sidebar → MCP Servers → Edit.

~/.continue/config.jsonjson

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "@cloudflare/mcp-server-cloudflare"
          ],
          "env": {
            "CLOUDFLARE_API_TOKEN": "${CLOUDFLARE_API_TOKEN}",
            "CLOUDFLARE_ACCOUNT_ID": "${CLOUDFLARE_ACCOUNT_ID}"
          }
        }
      }
    ]
  }
}

Continue uses modelContextProtocolServers with a transport block.

~/.codex/config.tomlshell

# ~/.codex/config.toml
[mcp_servers.cloudflare]
command = "npx"
args = [
  "-y",
  "@cloudflare/mcp-server-cloudflare",
]
env = { CLOUDFLARE_API_TOKEN = "${CLOUDFLARE_API_TOKEN}", CLOUDFLARE_ACCOUNT_ID = "${CLOUDFLARE_ACCOUNT_ID}" }

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

~/.config/zed/settings.jsonjsonc

{
  "context_servers": {
    "cloudflare": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@cloudflare/mcp-server-cloudflare"
        ]
      },
      "env": {
        "CLOUDFLARE_API_TOKEN": "${CLOUDFLARE_API_TOKEN}",
        "CLOUDFLARE_ACCOUNT_ID": "${CLOUDFLARE_ACCOUNT_ID}"
      }
    }
  }
}

Zed calls them "context_servers". Settings live-reload on save.

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. ChatGPT supports remote HTTPS MCP servers only — stdio servers must be hosted on a public HTTPS endpoint first.

2
Set required secrets
Set CLOUDFLARE_API_TOKEN, CLOUDFLARE_ACCOUNT_ID in your shell environment before launching your MCP client.
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

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

Security & scope

Access scope: Network
Sandbox: Authenticates with a Cloudflare API token; capabilities equal the token permissions (Workers, KV, R2, D1, DNS, etc).
Gotchas: A global API key grants every permission on the account — prefer scoped tokens with the minimum permissions needed.
Destructive operations (delete Worker, purge zone) run immediately; there is no confirmation layer.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.

Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.

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 against a real alternative. Swap the second MCP in [brackets] if you want a different match.

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

Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.

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 (CLOUDFLARE_API_TOKEN, CLOUDFLARE_ACCOUNT_ID) 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

— 2 updates tracked.

May 28, 2026
Refreshed install snippets and fact sheet; verified for 2026.
Mar 20, 2025
Initial directory listing.

At a glance

Maintainer: Cloudflare
Transport: stdioStreamable HTTP
Auth model: OAuth 2.1
Required secrets: CLOUDFLARE_API_TOKENCLOUDFLARE_ACCOUNT_ID
Supported clients: ChatGPT
Claude Desktop
Claude Code
Cursor
VS Code
Windsurf
Cline
Continue
Zed
Codex CLI
License: Apache-2.0
Language: TypeScript
Latest version: latest
Last verified: May 28, 2026

GitHub repo

Alternatives

Vercel →
Vercel — official ChatGPT Apps directory listing, verified for 2026.
Netlify →
Netlify — official ChatGPT Apps directory listing, verified for 2026.
Railway →
Spin up Railway projects, services, and deploys via remote MCP with OAuth.
Fly.io →
Run `fly mcp server` to expose flyctl operations to AI agents.
DigitalOcean →
Manage Droplets, App Platform, Kubernetes, and Spaces from an AI agent.
Name.com →
Register and manage Name.com domains via the official MCP, auto-generated from their OpenAPI.
GoDaddy →
Manage the largest consumer domain portfolio from inside ChatGPT — search, register, transfer, and DNS via OAuth.
Namecheap →
Search, register, and manage Namecheap domains from inside ChatGPT — OAuth install, no API key.

More Cloud & Infrastructure MCPs

Other tools in the same category worth evaluating.

Supabase

Full Supabase access: database, auth, storage, and edge functions.

supabasedatabasebackendpostgres

5 minLow

Stripe

Official

Manage payments, customers, and subscriptions through Stripe.

stripepaymentsbillingcommerce

5 minMedium

DigitalOcean

Official

Manage Droplets, App Platform, Kubernetes, and Spaces from an AI agent.

digitaloceanhostingcloudkubernetes

5 minMedium

Compared with Cloudflare

Side-by-side breakdowns for the choices people most often weigh against this MCP.

CloudflarevsVercel CloudflarevsNetlify CloudflarevsRailway CloudflarevsFly.io

Exploring Top MCPs for Cloud & Infrastructure? See all Cloud & Infrastructure MCPs →

Quick answer

What it does

Best for

Not for

Setup recipe

Install

Set required secrets

Try a minimum working prompt

Tools & permissions

Security & scope

Agent prompt pack

Full details

Frequently asked questions

Which API token permissions does it need?

Can it deploy Workers from source?

Is this safe to run against production DNS?

Does it support the Zero Trust / Access APIs?

What changed

More Cloud & Infrastructure MCPs

Supabase

Stripe

DigitalOcean

Compared with Cloudflare