Cloudflare MCP

Official Cloudflare MCP server — manage Workers, KV, D1, R2, and DNS through AI-powered conversation.

TRUSTED · Official

// Add to your client

{
  "mcpServers": {
    "cloudflare": {
      "command": "npx",
      "args": ["-y", "@cloudflare/mcp-server-cloudflare", "run", "<your-account-id>"]
    }
  }
}

{
  "mcpServers": {
    "cloudflare": {
      "command": "npx",
      "args": ["-y", "@cloudflare/mcp-server-cloudflare", "run", "<your-account-id>"]
    }
  }
}

claude mcp add cloudflare -- npx -y @cloudflare/mcp-server-cloudflare run <your-account-id>

Paste into your client's MCP configuration file.

// Try it now

"List all my Cloudflare Workers and show which ones were updated in the last week"

! Cloudflare API tokens should be scoped to specific zones and permissions — never use a global API key
! Deploying a Worker can replace the live production version — preview routes first
! DNS changes propagate globally — reverting mistakes can take minutes

Setup

Easy Setup

API key or simple config

Token usage

Light usage

// When to use

You're building on Cloudflare Workers and want AI help deploying and debugging
You need to manage KV, D1, or R2 data without using wrangler directly
You want to update DNS records or page rules quickly
You're setting up a new Cloudflare Worker project from scratch

// When NOT to use

You use AWS Lambda, Vercel Edge, or another edge platform
You need to edit Cloudflare Access policies with complex rules
You need enterprise-only features not exposed via the public API

// Usage Scenarios

Worker Deployment

Deploy or update a Worker and verify it's live.

Example prompt

"Deploy this Worker code to my-api.workers.dev and tell me when it's live"

KV & D1 Data Ops

Read and write data in KV namespaces or D1 databases.

Example prompt

"Query the users table in my D1 database and show rows where signup_date is today"

DNS Management

Add, update, or verify DNS records across your zones.

Example prompt

"Add a CNAME record for staging.mysite.com pointing to my-app.pages.dev"

// About

Plain English

Cloudflare runs huge parts of the internet — websites, small backend services, databases, file storage, and the rules that point a domain name to the right server. If you've ever followed a tutorial that said 'add a DNS record' or 'deploy a Worker,' that's Cloudflare. This server lets your AI assistant do all of that for you in plain English. Tell Claude 'deploy this code as a Worker named hello-api,' or 'add a CNAME record for staging.mysite.com pointing to my-app.pages.dev,' and it carries out the action. It can also read and write data in your KV stores and D1 databases, manage files in R2 storage, and check whether something you just deployed is live. For someone shipping a small product, this means you can keep building inside one conversation instead of jumping between dashboards and command-line tools. For someone learning, the AI explains what each change does before you commit. The trade-off: a misplaced command can take a production site down, so use a scoped API token, not a global one, and review actions before approving them.

The official Cloudflare MCP server gives AI assistants comprehensive access to Cloudflare's developer platform. Deploy and manage Workers, interact with KV and D1 databases, manage R2 storage, and configure DNS — through natural language.

Maintained by Cloudflare with growing API coverage. Essential for teams building on the Cloudflare stack.

GitHub 3.4kUpdated Feb 16, 2025MIT

View on GitHub Official Site