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 整合