Cloudflare

io.github.ofershapPublished by GitHub account ofershapv1.0.2Updated Oct 24, 2026

MCP server to manage Cloudflare Workers, KV, R2, Pages, DNS, and cache from your IDE

The publisher's own server: Cloudflare

VerifiedSTDIODesktop onlyCloud & InfrastructureDeveloper Tools

Overview

AI-generated overview

A local MCP server that lets an AI assistant manage Cloudflare zones, DNS records, Workers, KV, R2 buckets and cache purges from the IDE.

What you can do
List Cloudflare zones and their DNS records, and create or delete DNS records for a zone. List Workers scripts and delete a Workers script. List KV namespaces, list keys, read, write and delete KV values. List R2 storage buckets. Purge the cache for a zone, either everything or specific URLs.
When to use it
Useful when you want to inspect or change Cloudflare DNS, Workers, KV or cache settings from a chat with an assistant instead of the Cloudflare dashboard, for example to look up records or purge a URL's cache during debugging.
Requirements
Runs locally via npx from the npm package mcp-server-cloudflare-dns, so Node.js is needed. Requires a Cloudflare API token in CLOUDFLARE_API_TOKEN, and CLOUDFLARE_ACCOUNT_ID for Workers, KV and R2 operations. The token needs the relevant permissions, such as Zone:Read, Zone:Edit, Workers Scripts:Edit, Workers KV Storage:Edit and Zone:Cache Purge.
Before you install
The token grants real control over your Cloudflare account; scope it to only the permissions you need. Several tools change or delete live data: creating and deleting DNS records, deleting Workers scripts, writing and deleting KV keys, and purging cache. A wrong call can take a site or worker offline. Credentials are passed as environment variables in the client config.

Installation

In SourceWeft

  1. Open Cloudflare in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

MCP Server Cloudflare — Workers, KV, R2, DNS & Cache for AI Assistants

[npm version] [npm downloads] [CI] [License: MIT] [Agent Plugins]

An MCP server that lets your AI assistant manage Cloudflare Workers, KV, R2, DNS, and cache purging. Vercel, Railway, and Netlify all have MCP servers — now Cloudflare does too.

You: "List my Workers and purge cache for example.com"AI:  Found 3 Workers: api-gateway, auth-worker, image-resizer     ✅ Cache purged for https://example.com

Works with Claude Desktop, Cursor, and VS Code Copilot.

[MCP server Cloudflare demo — listing Workers and purging cache from Claude Desktop]

Tools

ToolWhat it does
cf_zonesList your Cloudflare zones (domains)
cf_dns_listList DNS records for a zone
cf_dns_createCreate a DNS record
cf_dns_deleteDelete a DNS record
cf_workers_listList Workers scripts
cf_worker_deleteDelete a Workers script
cf_kv_namespacesList KV namespaces
cf_kv_keysList keys in a KV namespace
cf_kv_getGet a value from KV
cf_kv_putWrite a value to KV
cf_kv_deleteDelete a KV key
cf_r2_bucketsList R2 storage buckets
cf_cache_purgePurge cache (all or specific URLs)

Quick Start

With Claude Desktop

Add to your claude_desktop_config.json:

json
{  "mcpServers": {    "cloudflare": {      "command": "npx",      "args": ["-y", "mcp-server-cloudflare-dns"],      "env": {        "CLOUDFLARE_API_TOKEN": "your_api_token",        "CLOUDFLARE_ACCOUNT_ID": "your_account_id"      }    }  }}

With Cursor

Add to your .cursor/mcp.json:

json
{  "mcpServers": {    "cloudflare": {      "command": "npx",      "args": ["-y", "mcp-server-cloudflare-dns"],      "env": {        "CLOUDFLARE_API_TOKEN": "your_api_token",        "CLOUDFLARE_ACCOUNT_ID": "your_account_id"      }    }  }}

Authentication

  1. Go to Cloudflare Dashboard > API Tokens
  2. Create a token with the permissions you need:
    • Zone:Read — for listing zones and DNS
    • Zone:Edit — for creating/deleting DNS records
    • Workers Scripts:Edit — for managing Workers
    • Workers KV Storage:Edit — for KV operations
    • Zone:Cache Purge — for cache purging
  3. Set CLOUDFLARE_API_TOKEN environment variable
  4. Set CLOUDFLARE_ACCOUNT_ID for Workers, KV, and R2 operations

Examples

Ask your AI assistant:

  • "List my Cloudflare zones"
  • "Show DNS records for zone xyz"
  • "Create an A record pointing to 1.2.3.4"
  • "List my Workers"
  • "Show KV keys in namespace abc"
  • "Purge the cache for https://example.com/page"
  • "List my R2 buckets"

Agent Plugins

This repo is an Agent Plugins 1.0.0 package: plugin.json, portable mcp.json, and skills/ ship together with the MCP server.

For Cursor, clone the repo and copy or symlink it to ~/.cursor/plugins/local/mcp-server-cloudflare, then reload the window. Skills and MCP show up under Customize > Plugins.

Agent Plugins v1 does not ship OAuth. Set CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID in your MCP client env (see Quick Start). One-click install is not offered because credentials stay in env.

Install and run via npm package mcp-server-cloudflare-dns (not the unrelated mcp-server-cloudflare stub on npm).

FAQ

What npm package do I install?

Use npx -y mcp-server-cloudflare-dns. The repo is named mcp-server-cloudflare on GitHub; npm publishes as mcp-server-cloudflare-dns.

Which env vars are required?

CLOUDFLARE_API_TOKEN for all API calls. CLOUDFLARE_ACCOUNT_ID for Workers, KV, and R2 tools.

Can I install it as an Agent Plugin in Cursor?

Yes, via ~/.cursor/plugins/local/mcp-server-cloudflare. Configure the same env vars in Cursor MCP settings.

What can this MCP manage?

Zones and DNS, Workers scripts, KV namespaces, R2 bucket listing, and cache purge for a zone.

Why no one-click Cursor button?

API token and account id cannot be embedded in a portable install link. Use the JSON under Quick Start.

Development

bash
npm installnpm testnpm run build

Author

[Made by ofershap]

[LinkedIn] [GitHub]


README built with README Builder

License

MIT © Ofer Shapira

Source: README.md at commit d9e1ea3

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Cloudflare integrations