Cloudflare MCP setup: documentation or account access

A question about Workers does not automatically require access to a Cloudflare account. Investigating a failure in a particular application needs the right operational context. Before connecting, write down one sentence describing the information you expect and how you will recognise a correct result. Keep that sentence beside the output during the first check.

Separate documentation from account access

Cloudflare maintains several remote MCP servers. The documentation endpoint is https://docs.mcp.cloudflare.com/mcp. The general API endpoint is https://mcp.cloudflare.com/mcp, with OAuth sign-in and permission selection. Additional endpoints focus on particular products. Copy the address for your chosen server from the provider’s list.

Start with documentation in VS Code

{
  "servers": {
    "cloudflare-docs": {
      "type": "http",
      "url": "https://docs.mcp.cloudflare.com/mcp"
    }
  }
}

This example defines an HTTP connection in a VS Code configuration. In an existing file, add the entry inside servers. Give a later account connection a different name so you can distinguish their tool lists. The VS Code guide explains the file. The separate configuration builder generates templates from registry declarations.

Check one documentation question

1. Choose a small question about a Workers feature you already know. Record the expected documentation page before using the connection.

2. Start the documentation server and inspect the tools offered. Ask about the selected feature and request a source URL.

3. Open the original source. Compare one concrete prerequisite or parameter with the response. A relevant heading alone is not sufficient evidence.

4. Record the server name, question and result without account data. Repeat the request with a second bounded question before reusing the findings.

Set up account access separately

For your own operational data, add a separate connection afterwards. Check the account and permitted resource scope during sign-in. Start with a familiar, non-sensitive resource and a read operation. Before any change, inspect the precise target resource and proposed action. The permission planner helps record those decisions so another person can reproduce your check later.

Cloudflare recommends the HTTP endpoint ending in /mcp for new connections. Do not infer the transport protocol solely from an older URL suffix. Check the documented transport and the client setting together. The troubleshooting navigator separates connection failures from access problems. Other implementations are available through registry search, and related guides through the app directory.

Common Cloudflare MCP questions

Which server is enough for documentation questions?

Start with the documented Docs endpoint. A question about public documentation does not need access to your account configuration.

Is the API connection automatically read-only?

No. Granted permissions and the requested operation determine the possible effect. Check both before accessing the account.

Why are there several Cloudflare endpoints?

The provider list separates general API access from product-specific connections. Choose according to your task.

Does the example confirm a working account connection?

No. It is a setup template for the documentation server. No authenticated account test was performed here.

Provider sources checked on 2 October 2026. The checks are proposals for your own environment.

1. Cloudflare MCP servers
   Show retrieval command

   curl -s https://developers.cloudflare.com/agents/model-context-protocol/cloudflare/servers-for-cloudflare/
2. Cloudflare repository
   Show retrieval command

   curl -s https://github.com/cloudflare/mcp-server-cloudflare

All posts