Cloudflare MCP Pro

io.github.helbertparanhos由 GitHub 账号 helbertparanhos 发布v1.1.0更新于 Oct 25, 2026

Cloudflare MCP: DNS, Zones, Workers, KV, R2, D1, Pages, WAF, SSL, Email, AI via REST API v4

发布方自己的服务:Cloudflare

已验证STDIO仅桌面数据库云端与基础设施

概览

AI 生成的概览

本地 MCP 服务器,让助手通过 Cloudflare REST API v4 管理 DNS、区域、Workers、存储、安全与 AI 等资源。

可以做什么
验证 API 令牌,列出账户、区域与区域设置,支持清除缓存和查询分析数据,列表工具可分页。管理 DNS 记录、DNSSEC 与 BIND 区域文件导出。部署和删除 Workers、路由、密钥与定时触发器。操作 KV 命名空间与键、R2 存储桶、D1 数据库与 SQL 查询,并查看 Pages 项目。处理 WAF 规则集、访问规则与页面规则、SSL 证书包、自定义主机名、电子邮件路由、Queues、Tunnels、Turnstile 与 Logpush。列出 Workers AI 模型并执行文本生成、嵌入、分类等推理。
适用场景
适合在本地会话中让助手查看或修改 Cloudflare 配置,例如编辑 DNS、部署 Worker、查询 D1 数据库或查看区域分析数据,尤其适用于脚本化或 CI 类工作流。
运行要求
以 npm 包形式通过 stdio 在本地运行(npx cloudflare-mcp-pro 或构建后的 dist 入口),需要 Node.js。需要在 CLOUDFLARE_API_TOKEN 中提供与所用操作匹配权限的 Cloudflare API 令牌;CLOUDFLARE_ACCOUNT_ID 与 CLOUDFLARE_API_BASE 为可选项。需要能访问 Cloudflare API 的网络。
安装前请注意
该令牌可实际控制你的 Cloudflare 账户,应尽量缩小权限范围。create、update、delete、deploy、purge_cache、query_d1、run_ai 等修改类工具需要 confirm: true,否则只返回预览而不执行;只读工具不受此限制。Worker 密钥会在预览和错误信息中被隐去,但批准前仍应逐项确认操作内容。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Cloudflare MCP Pro,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Cloudflare MCP Pro ☁️

MCP server for the Cloudflare REST API v4 — 69 tools across DNS, Zones, Workers, KV, R2, D1, Pages, Queues, Tunnels, SSL, WAF, Email Routing, Logpush and Workers AI in a single local stdio server authenticated by API token.

[npm version] [License: MIT] [GitHub Stars] [GitHub Forks] [GitHub Issues] [Glama Quality]

[TypeScript] [Node.js] [MCP] [Claude Code] [Cursor] [Claude Desktop]

[Instagram] [YouTube] [LinkedIn] [Buy Me A Coffee] [Strat Academy]

Unlike the official Cloudflare MCP offering (13 separate remote, OAuth-based servers), cloudflare-mcp-pro runs locally over stdio, authenticates with a single API token, and consolidates the most-used Cloudflare operations into one server with consistent verb_object tool names — ideal for Claude Code, CI, and scripted automation.

Features

  • DNS — list/create/update/delete records, DNSSEC, BIND zone-file export
  • Zones — list/get/create/delete, settings (SSL mode, HTTPS, min TLS…), cache purge, GraphQL analytics
  • Workers — deploy (ES module), routes, secrets, cron triggers, list/get/delete
  • KV / R2 / D1 — namespaces + key CRUD, bucket management, databases + SQL queries
  • Pages / Queues / Tunnels — list/get projects, queue management, tunnel inspection
  • Security — WAF rulesets, IP/ASN/country access rules, page rules, SSL certificate packs, custom hostnames (SaaS), Turnstile widgets
  • Email Routing — rules + destination addresses
  • Logpush — list/create jobs (zone or account scoped)
  • Workers AI — model catalog + inference (text generation, embeddings, classification)
  • Human-approval gate — every mutating tool requires confirm: true; without it the tool returns a non-executing preview (with secrets redacted) instead of acting (see below)
  • MCP annotations — every tool carries readOnly/destructive/idempotent hints so clients can gate dangerous actions
  • Auto-pagination — fetch_all: true on list tools follows every page
  • Single API-token auth, automatic retry + rate-limit (429/5xx) handling, and actionable error messages

Installation

bash
npm installnpm run build

Or run directly once published:

bash
npx -y cloudflare-mcp-pro

Configuration

Copy .env.example to .env and fill in:

VariableRequiredDescription
CLOUDFLARE_API_TOKEN✅API token from https://dash.cloudflare.com/profile/api-tokens
CLOUDFLARE_ACCOUNT_IDoptionalDefault account ID used when a tool doesn't receive account_id
CLOUDFLARE_API_BASEoptionalOverride the API base URL

Token scopes depend on what you use, e.g.: Zone:Read, DNS:Edit, Workers Scripts:Edit, Workers KV Storage:Edit, Workers R2 Storage:Edit, D1:Edit, Pages:Edit, Account Analytics:Read. Run the verify_token tool to confirm your token works.

Testing

Run the automated test suite (no network — fetch is mocked):

bash
npm test

It covers the human-approval gate, secret redaction, the security validations (hex IDs, path-segment encoding, model-id allowlist, purge mutual-exclusion, analytics hour-alignment), the API client (query serialization, 429 retry, error mapping, pagination + clamp, GraphQL non-JSON guard) and the Zod→JSON-Schema converter.

Interactive testing with the MCP inspector:

bash
npx @modelcontextprotocol/inspector dist/index.js

Add to Claude Code

In .claude/settings.json → mcpServers:

json
{  "mcpServers": {    "cloudflare-mcp-pro": {      "command": "node",      "args": ["projects/cloudflare-mcp-pro/dist/index.js"],      "env": {        "CLOUDFLARE_API_TOKEN": "your-token",        "CLOUDFLARE_ACCOUNT_ID": "your-account-id"      }    }  }}

Add to Claude Desktop

  • Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
json
{  "mcpServers": {    "cloudflare-mcp-pro": {      "command": "node",      "args": ["/absolute/path/projects/cloudflare-mcp-pro/dist/index.js"],      "env": {        "CLOUDFLARE_API_TOKEN": "your-token",        "CLOUDFLARE_ACCOUNT_ID": "your-account-id"      }    }  }}

Human-approval gate

Every mutating tool (any create_*, update_*, delete_*, deploy_*, put_*, edit_*, purge_cache, query_d1, run_ai, …) is gated server-side. Read-only tools (list_*, get_*, verify_token, export_dns_records, analytics) are never gated.

  • Calling a mutating tool without confirm: true returns a confirmation_required preview describing the tool, the risk level, and the (secret-redacted) arguments — and does not execute.
  • Re-call the same tool with "confirm": true to actually perform it, after a human has approved.

This gate is enforced in the server regardless of the MCP client, and works alongside the MCP annotations (destructiveHint) that prompt the human in compatible clients like Claude Code. Secret values (e.g. Worker secret text) are redacted from previews and never appear in error messages.

jsonc
// 1) preview (no confirm) → nothing happensdelete_zone { "zone_id": "..." }// → { "status": "confirmation_required", "risk": "DESTRUCTIVE — ...", ... }
// 2) after human approvaldelete_zone { "zone_id": "...", "confirm": true }   // actually deletes

Tools (69)

List tools accept fetch_all: true to follow pagination. Mutating tools accept confirm: true (see the gate above). Every tool advertises MCP annotations (readOnlyHint / destructiveHint / idempotentHint).

Account — verify_token, list_accounts

Zones & settings — list_zones, get_zone, create_zone, delete_zone, purge_cache, get_zone_analytics, get_zone_setting, update_zone_setting

DNS — list_dns_records, create_dns_record, update_dns_record, delete_dns_record, get_dnssec, edit_dnssec, export_dns_records

Workers — list_workers, get_worker, deploy_worker, delete_worker, list_worker_routes, create_worker_route, delete_worker_route, put_worker_secret, delete_worker_secret, update_worker_cron

KV — list_kv_namespaces, create_kv_namespace, kv_list_keys, kv_get, kv_put, kv_delete

R2 — list_r2_buckets, create_r2_bucket, delete_r2_bucket

D1 — list_d1_databases, create_d1_database, query_d1

Pages — list_pages_projects, get_pages_project

WAF & firewall — list_firewall_rulesets, get_ruleset, list_access_rules, create_access_rule, delete_access_rule

Page rules — list_page_rules, create_page_rule, delete_page_rule

SSL/TLS — list_certificate_packs, get_ssl_verification, order_certificate_pack

Custom hostnames (SaaS) — list_custom_hostnames, create_custom_hostname, delete_custom_hostname

Email Routing — list_email_rules, create_email_rule, list_email_destinations

Queues — list_queues, create_queue, delete_queue

Tunnels — list_tunnels, get_tunnel

Turnstile — list_turnstile_widgets, create_turnstile_widget

Workers AI — list_ai_models, run_ai

Logpush — list_logpush_jobs, create_logpush_job

Author

Helbert Paranhos / Strat Academy — stratacademy.com.br

License

MIT — see LICENSE.

来源:README.md,提交 352c8ed

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v1.1.0最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Cloudflare 集成