← MCP

Cloudflare MCP ServerCloudflare MCP Server

Cloudflare

MCPMCP 云平台Cloud platform WorkersWorkers Apache2.0Apache2.0 远程托管Remote-hosted 受限tokenScoped token partial lifecycle: active 核验Checked 2026-10-30

Cloudflare 官方 MCP server（Apache-2.0）：agent 写 Worker、部署、管 D1/R2/DNS、查官方 docs。提供受限 token——但记住「能部署=能跑任意代码」，token 要按最小面配。

Cloudflare's official MCP server (Apache-2.0): agents write Workers, deploy, manage D1/R2/DNS, search official docs. It has the finest restricted-token granularity in its class — but remember 'can deploy = can run arbitrary code'; scope tokens to the minimum.

适合与不适合When to use it, when not to

适合：Cloudflare 栈的部署-调试闭环接 agent。不适合：要「只读配置」硬边界（能收窄但要仔细配 token）。

Fits: deploy-debug loops on the Cloudflare stack plugged into agents. Not a fit: a hard 'config only, no deploy' boundary (narrowable, but token config must be careful).

中文生态China availability 国产 / 国内可直接用 / 备案状态 · 快照domestic / direct access / CAC filing · snapshot 2026-10-21

出品属地Origin: 国外出品foreign-made　Cloudflare, Inc.（美国）。Cloudflare, Inc. (US).
国内使用Direct access: 直连不可达direct blocked　github.com 直连实测 000（波动，同日代理可达 200）；developers.cloudflare.com 直连未单独测。github.com measured 000 direct (fluctuating; 200 via proxy the same day); developers.cloudflare.com not individually measured.
备案状态CAC filing: 未见于备案名单not in filing list：未见于网信办公示名单（2026-10-21 检索）；该产品未面向大陆公众提供服务，备案不适用。not in the CAC public registry (searched 2026-10-21); the product does not serve the mainland public, so filing does not apply.

备案信息以网信办《生成式人工智能服务已备案信息》公示名单为准（按批次滚动更新，本站只抄编号不解读）；「大陆可直连」是本站从大陆网络直连实测的结果，不是厂商承诺。GitHub 类站点当日实测有波动，口径写在依据里。Filing status is quoted from the CAC public registry (updated batch by batch; this site copies the number and does not interpret it). "Direct access" is this site's own reachability measurement from a mainland network, not a vendor promise. GitHub-hosted sites fluctuated on the measurement day — the note says so.

固定坐标系Fixed coordinate system

11 个维度dimensions, 与同分区其他对象逐项可比each comparable item by item against others in the same section.

模型与开放条件Model & openness: 它自己不调模型——被 MCP 客户端调用的接口实现。它把 Cloudflare 平台（Workers、Pages、D1、R2、DNS、docs 检索等）包装成工具给 agent 用。
It calls no model itself — an interface implementation called by MCP clients. It wraps the Cloudflare platform (Workers, Pages, D1, R2, DNS, docs retrieval, etc.) as tools for agents.
运行位置Where it runs: 官方托管远程 server 为主（docs 有远程端点线）+ 本地可跑；GitHub 4,431★，最近推送 2026-10-22（API 核验）。
Primarily an official hosted remote server (the docs carry a remote-endpoint line) + runnable locally; GitHub 4,431★, last push 2026-10-22 (API verified).
本地文件Local files: 不读写本机项目文件——作用域是 Cloudflare 账户资源（部署 Workers、写 D1/R2 等）。
Reads and writes no local project files — the scope is Cloudflare account resources (deploying Workers, writing D1/R2, etc.).
关机后的任务Tasks after shutdown: 远程形态在 Cloudflare 侧；无后台任务语义（部署动作即时完成）。
The remote form lives on Cloudflare's side; no background-task semantics (deploy actions complete immediately).
工具与扩展Tools & extensions: 按产品分组（Workers/Pages/D1/R2/DNS/Docs…）可裁剪启用；写能力齐全（部署 Worker、建 KV/D1 库、改 DNS 记录）。完整分组以仓 README 为准。
Grouped by product (Workers/Pages/D1/R2/DNS/Docs…), trimmable via configuration; write capability is complete (deploying Workers, creating KV/D1 databases, changing DNS records). The complete grouping follows the repo README.
上下文与记忆Context & memory: 无跨会话记忆——状态在 Cloudflare 账户资源本身。
No cross-session memory — state lives in the Cloudflare account resources themselves.
权限与限制Permissions & limits: API token 权限=agent 权限：Cloudflare token 可细粒度限定资源与操作面—— 官方推荐用受限 token 接 MCP。这是同类里凭据粒度做得最细的一条线，但「能部署代码到 Workers」意味着能跑任意代码——按此最坏面设防。
API-token permissions = agent permissions: Cloudflare tokens can narrowly restrict resources and operation surfaces — the official recommendation is to connect MCP with a restricted token. This is the finest-grained credential line among its peers, but "able to deploy code to Workers" means able to run arbitrary code — defend against that worst case.
适合什么任务Best for: 适合：Cloudflare 栈的 agent 部署流（写 Worker→部署→查日志）、docs 检索。不适合：要「只配置不部署」的硬边界（token 粒度能收窄但要仔细配）。
Fits: the agent deployment flow on the Cloudflare stack (write Worker → deploy → check logs), docs retrieval. Not a fit: a hard "configure but never deploy" boundary (token granularity can narrow it, but must be configured carefully).
传输方式Transport: 远程 Streamable HTTP（官方托管端点）+ 本地 stdio 两线；端点矩阵按产品分组（每产品一个远程 server URL）——以仓 README 为准。核验：仓与 developers.cloudflare.com/changelog（2026-10-21）。
Remote Streamable HTTP (official hosted endpoints) + a local stdio line; the endpoint matrix is grouped by product (one remote server URL per product) — follows the repo README. Verified against: the repository and developers.cloudflare.com/changelog (2026-10-21).
认证机制Authentication: Cloudflare API token（建议受限 token：限定账户/资源/操作）； OAuth 线支持状态未逐条核验。
A Cloudflare API token (a restricted token is recommended: limit account/resources/operations); OAuth-line support status not verified item by item.
权限范围Permission scope: 读面：docs 检索、资源查询；写面：部署 Workers、建/改 D1/R2/KV、DNS 记录变更。 token 粒度是主收紧手段；无工具级审批机制的官方说明。
Read surface: docs retrieval, resource queries; write surface: deploying Workers, creating/modifying D1/R2/KV, DNS record changes. Token granularity is the primary tightening control; no official statement of a tool-level approval mechanism.

头号误解Top misconception

用全权限全局 API key 接 agent——官方推荐受限 token，粒度差别巨大Plugging a full-scope global API key into an agent — the official recommendation is restricted tokens; the granularity difference is huge
把「部署 Worker」当配置操作——那是往边缘跑任意代码的写面Treating 'deploy a Worker' as a config operation — that is pushing arbitrary code to the edge
工具分组裁剪当审批层——裁剪是收窄暴露面，不是逐操作确认Reading tool-group trimming as an approval layer — trimming narrows exposure; it is not per-operation confirmation

未知项清单Known unknowns

产品分组全表与远程端点矩阵（未逐条清点）
OAuth 支持状态（未逐条核验）
各端点速率限制（未逐条核验）

The full product-grouping table and remote endpoint matrix (not enumerated item by item)
OAuth support status (not verified item by item)
Rate limits of each endpoint (not verified item by item)

证据来源Evidence sources

判断可回到以下一手源复核。本站核验日Every judgement can be rechecked against the primary sources below. Verified on 2026-10-30，内容更新日content updated on 2026-10-21。

类型Type	名称Name	链接Link
repo	cloudflare/mcp-server-cloudflare · 仓库（Apache-2.0；4,431★，最近推送 2026-10-22，GitHub API 核验）cloudflare/mcp-server-cloudflare · repository (Apache-2.0; 4,431★, last push 2026-10-22, GitHub API verified)	https://github.com/cloudflare/mcp-server-cloudflare
changelog	cloudflare/mcp-server-cloudflare · Releases（changelog）cloudflare/mcp-server-cloudflare · Releases (changelog)	https://github.com/cloudflare/mcp-server-cloudflare/releases
changelog	Cloudflare · 开发者 changelog（changelog）Cloudflare · developer changelog	https://developers.cloudflare.com/changelog/

实测记录Measured runs

本档未在真实客户端逐项跑通；工具清单与权限来自官方 README。

This site has not completed measured runs. The test protocol is at protocols/mcp/_protocol.md.