M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
C

Cloudflare MCP Server

Official
Manage your Cloudflare account in natural language via remote MCP servers
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #133 of 438
Stars
★ 4.4k Very popular
Transport
Streamable HTTP
Runtime
Hosted (no local runtime)
Credentials
Optional API key
License
Apache-2.0
Last commit
59FMRS · C

An official Cloudflare collection of remote MCP servers split by product domain, each served over Streamable HTTP with OAuth or API-token authentication — well suited to teams already on Cloudflare who want natural-language account management, provided API tokens are scoped with least privilege given the real account-level permissions involved.

Strongest · Maintenance 14/20 Weakest · Reliability 8/20

Reliability
8/20
Security and permissions
11/20
Maintenance
14/20
Documentation
13/20
Setup experience
13/20
Why each score
Reliability 8/20
The README describes a unified stateless Streamable HTTP handler (/mcp with an /sse compatibility alias) and explains that OAuth, credentials, account selection, and product state live in application-layer Durable Objects — the architecture description is coherent. However, server.json declares no tools at all, so declared tool behavior cannot be checked against real behavior, and no CI workflow files or committed tests are present in the provided material as verifiable execution evidence. Per the static calibration rule, reliability is capped at 12 without CI+test evidence, and the 16 remote endpoints with a mixed optional-Bearer/OAuth auth story add further uncertainty. Scored 8: the happy path is plausible from the description, but error handling, edge cases, and reproducibility lack supporting evidence.
Security and permissions 11/20
Most remote endpoints authenticate via an optional Authorization Bearer header or OAuth, with the key field marked is_secret — a reasonable credential-handling pattern with no hardcoded tokens or obvious leakage. The README shows an example of creating a scoped, minimal-permission API token for a specific service (Browser Rendering), indicating some least-privilege awareness. However, the material does not disclose whether destructive or irreversible operations (DNS changes, Workers deployments, container spin-up, audit log export, etc.) require confirmation, and the Bearer token grants are described only at a broad User/Account level without per-domain scoping detail across the 16 product areas. No red-line issue is present (no malware, credential theft, or fabricated results), so it does not fall into the 0-4 band, but incomplete evidence on confirmation flows and permission scoping caps it at 11.
Maintenance 14/20
The repository uses the Apache-2.0 license, the README references a CONTRIBUTING.md indicating a contribution process, and with 4,028 stars, 53 open issues, no archival, and an 'active' status field in the manifest, it shows clear signs of active maintenance. However, the provided material contains no concrete release history, commit cadence, dependency-update policy, or dedicated security-response channel, leaving governance details incomplete. Scored 14: active but without enough evidence of versioning/security-response process for a higher score.
Documentation 13/20
The README provides a service table with URLs and subfolder links, connection instructions, an OpenAI Responses API integration example (with a permission-scope screenshot), a troubleshooting section (context-length interruptions), and a note on paid features — a reasonably layered set of docs. However, it lacks per-tool parameter/response documentation, rate-limit or cost specifics, and repeats the same generic Authorization description across all services rather than detailing per-domain usage examples or known limitations. Scored 13.
Setup experience 13/20
Because all servers are hosted remote Streamable HTTP endpoints, users simply plug a URL into any MCP client with remote-server support (or the Cloudflare AI Playground) — no local runtime is required, which is a genuine ease-of-use advantage. Per the static calibration rule, setup is capped at 15 absent verifiable CI/test execution evidence; additionally, the material does not detail the concrete OAuth authorization interaction steps or local development setup (it only references an external CONTRIBUTING.md without expanding on it). Scored 13.

Static review · not runListed 2026-08-06

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkChanges third-party account dataControls a browserConnects to a database

Best for

  • Teams already using Cloudflare products who want to manage their account via natural language
  • Workflows that benefit from curated, typed tools scoped to a single Cloudflare product area (observability, DNS, bindings, etc.)
  • Users who want a remotely hosted MCP integration rather than a self-hosted/local server

Not for

  • Workflows needing broad API coverage across many Cloudflare products via code execution (use Cloudflare's Code Mode server, cloudflare/mcp, instead)
  • Users without a Cloudflare account, or who don't want to grant a third-party MCP client access to their account
  • Scenarios requiring a fully offline or locally-run MCP server, since all listed servers are remotely hosted

Required permissions

  • Optional Cloudflare API key passed as a Bearer token in the Authorization header, used when not authenticating via OAuth; supports user- or account-owned tokens
  • OAuth authorization flow supported for connecting an account
  • The Documentation server (docs.mcp.cloudflare.com) requires no auth header, serving public documentation lookups

Risks and side effects

  • Each server maps to a different Cloudflare product domain; an overly broad API token scope could grant an MCP client more account access than a given task actually needs
  • Some tools can make real changes to account configuration on the user's behalf, so misinterpreted natural-language instructions could cause unintended production changes
  • Account credentials (API tokens) are transmitted as Bearer headers between the client and the remote service, so the client environment must be kept secure
  • Some features may require a paid Cloudflare Workers plan

Setup

Before you start

Runtime：Hosted (no local runtime)

In an MCP client that supports remote servers (e.g. Cursor, Claude Desktop, or Cloudflare AI Playground), add the URL for the desired product-domain server (e.g. https://docs.mcp.cloudflare.com/mcp, https://bindings.mcp.cloudflare.com/mcp) — no local installation is required. Most servers support OAuth login; alternatively, supply a Cloudflare API key (user- or account-owned token) as a Bearer token in the Authorization header. To use a server via the OpenAI Responses API, create a Cloudflare API token scoped with the permissions that specific server requires.

Check that it works

Add https://docs.mcp.cloudflare.com/mcp to an MCP client with remote-server support (e.g. Cursor or Claude); on success the documentation server's tools should appear, or ask a Cloudflare docs question and get an up-to-date answer.

Troubleshooting

  1. If you see "Claude's response was interrupted," the client likely hit its context-length limit from many chained tool calls (most common on the observability server) — break requests into smaller, more specific tool calls
  2. Confirm the connected server URL matches the intended product domain (each domain has its own subdomain)
  3. Verify the Cloudflare API token's scopes match what the target server requires
  4. Check whether the account has the paid Cloudflare Workers plan required for the feature in question

Things to try

Once connected, you can ask your AI assistant things like:

  • Search the Cloudflare docs for how Workers KV works
  • Show me recent logs and errors from my Workers application
  • Fetch this web page, convert it to markdown, and take a screenshot
  • Query my recent audit logs and generate a report

Use cases

Look up current Cloudflare product documentation
Build and inspect Workers storage, AI, and compute bindings
Check the status and health of Workers Builds
Debug application logs and observability analytics
Fetch web pages, convert them to markdown, or take screenshots
Summarize Logpush job health and search AI Gateway logs
Query audit logs and generate compliance reports
Analyze DNS performance and SaaS security misconfigurations (CASB)

Supported clients

Claude
Cursor
OpenAI Responses APIPartial support

Listed from the project's documentation, not tested by this site.

Overview

An official Cloudflare-maintained repository providing a set of domain-specific remote MCP servers (Documentation, Workers Bindings, Workers Builds, Observability, sandbox Containers, Browser Rendering, Logpush, AI Gateway, AutoRAG, Audit Logs, DNS Analytics, DEX, CASB, Radar, Blog, Demo Day, and more). Each server exposes the same stateless request handler over Streamable HTTP at its own *.mcp.cloudflare.com/mcp subdomain; the /sse path remains only as a URL compatibility alias and does not use the deprecated HTTP+SSE transport. Any MCP client with remote-server support (e.g. Cursor, Claude, Cloudflare AI Playground) can connect directly to these URLs to read account configuration, process information, and make suggested changes across Cloudflare's application, security, and performance products.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 64.1k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision a21972e21928 Data synced 2026-11-04 Read the FMRS scoring method