Set up the Cloudflare Documentation MCP Server

The Cloudflare Documentation MCP Server connects AI clients like Claude Code, Codex, and Cursor to a semantic search over the complete Cloudflare developer documentation — publicly reachable and requiring no sign-in. This guide covers setup and how it differs from the account-bound Cloudflare API MCP Server.

Connect the server

For Claude Code, a single command is enough: claude mcp add --transport http cloudflare-docs https://docs.mcp.cloudflare.com/mcp. The server is then available the next time the client starts. Clients without native remote MCP support can connect through the bridge npx -y mcp-remote@latest https://docs.mcp.cloudflare.com/mcp. No sign-in, API token, or Cloudflare account is needed anywhere in this flow.

Ask your first questions

After setup, you can ask the agent concrete development questions directly — about Workers pricing logic, R2 bucket configuration, or Workers AI Search binding usage. The server searches the currently indexed Cloudflare documentation and returns context-aware excerpts instead of general, potentially outdated model knowledge.

Distinction from the Cloudflare API MCP Server

If you also need read or write access to your own Cloudflare account — checking DNS records or managing Workers, for example — you need the separate Cloudflare API MCP Server with OAuth sign-in. This Documentation server deliberately stays limited to pure documentation search, keeping it low-risk and instantly usable.