cloudflare

mcp-server-cloudflare: Connect AI Clients to Cloudflare Services

A TypeScript collection of Model Context Protocol (MCP) servers that connects AI clients to Cloudflare services through product-specific tools. Use it for guided interactions with Cloudflare products, or choose Cloudflare’s separate API MCP server for broader API access.

ActiveTypeScriptApache-2.0AI AgentsMCPMCP Server
View on GitHub Compare
Stars
4.4k
Forks
562
Stars, last 30 days
+88
Last commit
7 days ago
Contributors
43

Our take

Activeregular commits and releases

Health score

73/100

How it is scored
Activity
76
Community
80
Issues
67
Pull requests
70

+88 stars in the last 30 days

  • Releases more often than 93% of the projects we track

This is an actively maintained, Apache-2.0-licensed collection for teams that want focused Cloudflare tools in MCP clients, with a healthy contributor base and frequent releases.

Good fit if

  • You use an MCP client and want guided tools for specific Cloudflare product areas.
  • Your work involves Cloudflare documentation, Browser Run, containers, Digital Experience Monitoring, or CASB.
  • You want a project with recent commits and releases, and contributions spread across many contributors.

Look elsewhere if

  • You need broad Cloudflare API access through code execution, which the project directs users to get from cloudflare/mcp.
  • Your MCP client cannot connect to remote Streamable HTTP servers.
  • You need one of the deprecated product servers as a supported long-term option, since the README recommends migrating to the Cloudflare API MCP Server.
All health signals
Last commit2026-10-22 (7 days ago)
Commits, last 90 days30
Releases, last 12 months100+ (latest workers-observability@0.6.0, 2026-10-22)
Contributors43 (top contributor: 15% of commits)
Issues closed, last 90 days18 (typically closed in 3 days)
Pull requests merged, last 90 days30 (typically merged in 0 days)
Project age23 months

Checked on 2026-10-30 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

4,456

Forks

575

Change since Nov 9, 2026: +2 stars·+1 forks

Overview

mcp-server-cloudflare is a collection of Model Context Protocol (MCP) servers built for Cloudflare services. It lets compatible clients such as Cursor and Claude use natural language to read account configuration, inspect information, and, where supported, make changes across Cloudflare product areas.

The repository focuses on product-specific servers, including documentation search, containers, Browser Run, Digital Experience Monitoring, and Cloudflare One CASB. These remote servers expose stateless Streamable HTTP endpoints at /mcp. For broad Cloudflare API access through code execution, the project recommends Cloudflare’s separately maintained cloudflare/mcp instead.

Key Features

  • Connect MCP clients to remote Cloudflare product-specific servers.
  • Query Cloudflare documentation and Cloudflare Blog content.
  • Use Browser Run to fetch pages, convert them to Markdown, and take screenshots.
  • Create sandbox development environments with the container server.
  • Inspect Digital Experience Monitoring data and Cloudflare One CASB misconfigurations.
  • Use stateless Streamable HTTP handlers at /mcp without an MCP protocol session.
  • Retired /sse endpoints respond with a 410 Gone message directing clients to /mcp.

Use Cases

  • A developer using an MCP-compatible client can consult current Cloudflare documentation while working with Cloudflare services.
  • A team investigating an application can use the Digital Experience Monitoring server for quick insight into critical applications.
  • A web developer can fetch and review pages or take screenshots through Browser Run.
  • A security team can use the CASB server to identify SaaS application misconfigurations.
  • A developer who wants broad Cloudflare API coverage can compare this collection with the recommended cloudflare/mcp server.

What you need

Detected in the repository

  • Node.js (from package.json)
  • Automated checks on GitHub Actions

License in plain words

Apache-2.0permissive

  • Commercial use: yes
  • Modify and redistribute: yes
  • You must keep: the license, the NOTICE file and a note of your changes
  • Share your changes: no
  • Includes an explicit patent grant from the contributors:

A summary, not legal advice: the LICENSE file is what applies.

Getting Started

Connect a remote-server-capable MCP client to a server URL listed in the README. For example, the documentation server is available at https://docs.mcp.cloudflare.com/mcp. See the README for client setup and API token permissions.

Considerations

  • The project requires Node.js to run locally; the supplied project facts indicate CI is configured but do not report tests.
  • Some features may require a paid Cloudflare Workers plan. Access through the OpenAI Responses API also requires a Cloudflare API token with the relevant permissions.
  • Several product-specific servers are marked deprecated in the README, which recommends migrating to the separate Cloudflare API MCP Server.
  • The README notes that chained tool calls can cause context-length interruptions in clients such as Claude; shorter, more specific requests may help.
  • Cloudflare account configuration, credentials, and product-specific state may be involved. Review the required permissions and account access before connecting a client.

Found this useful?

Share it with someone who would like mcp-server-cloudflare.

Comparisons

mcp vs mcp-server-cloudflare