Full Supabase access: database, auth, storage, and edge functions.
supabasedatabasebackendpostgres
Cloudflare
Manage Workers, R2 buckets, DNS, and edge policies on Cloudflare.
Install Cloudflare
— pick your client, copy, paste.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-cloudflareRun 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 → Developer modejson
{
"name": "Cloudflare",
"transport": "stdio",
"command": "npx",
"args": [
"-y",
"@cloudflare/mcp-server-cloudflare"
],
"env": {
"CLOUDFLARE_API_TOKEN": "${CLOUDFLARE_API_TOKEN}",
"CLOUDFLARE_ACCOUNT_ID": "${CLOUDFLARE_ACCOUNT_ID}"
}
}Enable Developer mode (paid plans) and enter these values in the UI.
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
- 1
Install
Copy the install snippet for your client from the Install section above.
- 2
Set required secrets
Set
CLOUDFLARE_API_TOKEN,CLOUDFLARE_ACCOUNT_IDin 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 [Supabase 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 Supabase
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.Refreshed install snippets and fact sheet; verified for 2026.
Initial directory listing.
More Cloud & Infrastructure MCPs
Other tools in the same category worth evaluating.
Exploring Top MCPs for Cloud & Infrastructure? See all Cloud & Infrastructure MCPs →