Cloudflare's own hosted servers, starting with a docs search that needs no sign-in.
- Needs your setup first
- ★ 4.4K GitHub stars
- Last commit 22 Oct 2026
At a glance
Cloudflare runs a family of remote MCP servers, each at its own address and each signing in to your account with OAuth where it needs to. The documentation server we list below is the simplest: it searches the current Cloudflare docs and needs no account. Others fetch and screenshot pages through Browser Run, start a sandboxed container for running code, read the Cloudflare blog, and check Zero Trust and SaaS settings.
For broad control of an account, Cloudflare now recommends a separate server at mcp.cloudflare.com, which covers its whole API through code execution. Several older single-product servers, such as Workers Bindings and DNS Analytics, are deprecated in its favour.
- Made by
- Cloudflare
- GitHub stars
- 4.4K
- Last commit
- 22 Oct 2026
- Tools
- 2
- Runs on
- Hosted
Our check: It needs something our Linux test machine does not have (an account, a desktop app, a Mac or a running service), so on 27 Oct 2026 we read its tools from the source code instead of running this config. Nothing to install: Cloudflare hosts every server in this repository. The shared database also listed "npx mcp-remote", which is only a bridge for clients that cannot use a URL.
What's in the pod: its tools
We found 2 tools in its source code on 27 Oct 2026. Every one of them only reads, so nothing changes unless you act on what it finds.
How we tested it: Read from the source of the documentation server in cloudflare/mcp-server-cloudflare, because our test network could not reach docs.mcp.cloudflare.com. The other servers in the family each have their own tools.
Only reads2 tools · Looks things up and changes nothing.
| Tool | What it is for |
|---|---|
migrate_pages_to_workers_guide | Hands the model Cloudflare's guide for moving a Pages project to Workers, to read before it starts. |
search_cloudflare_documentation | Searches the current Cloudflare developer docs and returns the closest matching passages with their links. |
Tool groups
docs.mcp.cloudflare.com- Documentation search, listed above. No sign-in.
mcp.cloudflare.com- The Cloudflare API server, kept in the cloudflare/mcp repository. Broad access to your account's APIs through code the model writes and runs. Recommended for account work.
browser.mcp.cloudflare.com- Browser Run: fetch pages, turn them into markdown and take screenshots on Cloudflare's browsers.
containers.mcp.cloudflare.com- A sandboxed container where the model can run commands and code.
blog.mcp.cloudflare.com- Search and read posts on the Cloudflare blog.
dex.mcp.cloudflare.com, casb.mcp.cloudflare.com- Zero Trust tools: Digital Experience Monitoring insights and CASB checks of SaaS apps.
Deprecated- AI Gateway, Audit Logs, AutoRAG, DNS Analytics, GraphQL, Logpush, Observability, Radar, Workers Bindings and Workers Builds. They still answer, but Cloudflare asks you to move to the API server.
Grouped and described by us. The README on GitHub lists the inputs each tool takes.
Set it up
Pick your app for the exact snippet and where it goes.
Where it goes: Settings → Connectors → Add custom connector
https://docs.mcp.cloudflare.com/mcpPaste the URL and sign in if asked. Custom connectors depend on your plan.
Where it goes: Your terminal, in the project folder
claude mcp add --transport http cloudflare https://docs.mcp.cloudflare.com/mcpWhere it goes: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
"mcpServers": {
"cloudflare": {
"url": "https://docs.mcp.cloudflare.com/mcp"
}
}
}Where it goes: .vscode/mcp.json in your project
{
"servers": {
"cloudflare": {
"type": "http",
"url": "https://docs.mcp.cloudflare.com/mcp"
}
}
}Where it goes: ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"cloudflare": {
"serverUrl": "https://docs.mcp.cloudflare.com/mcp"
}
}
}Where it goes: Settings → Apps & Connectors → create a connector
https://docs.mcp.cloudflare.com/mcpPaste the URL as the connector address and sign in if asked.
Swap the address for another server in the family, such as https://browser.mcp.cloudflare.com/mcp or https://containers.mcp.cloudflare.com/mcp. The old /sse addresses no longer work.
Remote option
The Cloudflare API server, which Cloudflare recommends for working on your account. It signs in with OAuth.
https://mcp.cloudflare.com/mcpNew to this? See the setup guides for Claude Code, Cursor, Claude Desktop and ChatGPT.
Settings
Names are exactly as the project spells them. Required ones are marked.
| Setting | What it does |
|---|---|
Server URLConfig · required | Each server has its own address ending in /mcp. Pick the one for the job, or add several.https://browser.mcp.cloudflare.com/mcp |
OAuth sign-inConfig | Servers that touch your account open a Cloudflare sign-in in the browser the first time and ask which account to use. |
API tokenConfig | For tools that cannot do OAuth, such as the OpenAI Responses API, send a Cloudflare API token with the scopes that server needs as a Bearer header. |
npx mcp-remoteConfig | A bridge for clients that only start local commands.npx mcp-remote https://docs.mcp.cloudflare.com/mcp |
What it can touch
It can read
- Cloudflare's public docs and blog
- Your account's settings, logs and analytics, on the servers you sign in to
It can change
- Account resources through the API server or the older product servers, within the access you grant at sign-in
- Nothing at all on the docs and blog servers
Safer setup: Start with the docs server, which needs no account. When you connect account servers, sign in with an account or token that has only the permissions the task needs.
Before you start
- A client that connects to remote servers by URL, or npx mcp-remote
- A Cloudflare account for every server except docs and blog
If it does not work
- An old config returns 410 Gone
- The /sse addresses were retired. Use the same host with /mcp on the end.
- The reply stops half way
- The model likely ran out of context after many tool calls. Ask narrower questions or split the request.
- A tool says it needs a paid plan
- Some features, such as parts of Workers, need a paid Workers plan on the account.
- Your client cannot add remote servers
- Use npx mcp-remote with the server URL as a local command.
Peas in a pod: similar servers
How Cloudflare MCP Servers lines up against other cloud and operations servers on the shelf.
| Server | Tools | Runs on | Licence | Stars |
|---|---|---|---|---|
| Cloudflare MCP Servers | 2 | Hosted | – | 4.4K |
| Grafana MCP | 62 | Your computer | Apache-2.0 | 3.6K |
| Azure DevOps MCP | 44 | Your computer or hosted | MIT | 2.1K |
| AWS Knowledge MCP Server | 5 | Hosted | – | 9.8K |
Questions
Which Cloudflare server should I start with?
The docs server for questions, and the Cloudflare API server at mcp.cloudflare.com for working on your account. The product servers suit narrow, guided jobs.
Do I need to install anything?
No. Cloudflare hosts all of them; you only add the URL to your client.
Is it free?
The servers cost nothing to connect to. Using them is billed like any other use of the Cloudflare products behind them.
Can I run my own copy?
Yes. The source is on GitHub under Apache-2.0 and deploys to Cloudflare Workers.
Something wrong on this page? Tell us.
