Cloudflare MCP

Cloudflare's own MCP server for the entire Cloudflare API. Instead of loading thousands of tool definitions, your agent writes small pieces of JavaScript: one searches Cloudflare's API spec for the right endpoints, the next calls them, and only the result comes back. It can also search Cloudflare's developer docs. What you can do with it - List and manage Workers, KV namespaces, R2 buckets and D1 databases - Add and change DNS records - Work with Pages, Firewall rules, Load Balancers, Stream, Images, AI Gateway, Vectorize, Access and Gateway - Look up answers in Cloudflare's developer documentation - Check which Cloudflare user or account you're connected as How it connects Cloudflare hosts it at https://mcp.cloudflare.com/mcp. Connect with OAuth: you're sent to Cloudflare to sign in and choose the permissions it gets. For CI or automation, you can use a Cloudflare API token as a bearer token instead. If a call needs a permission you didn't grant, it asks you to re-authorize with that scope added. Good to know Each result is capped at about 6,000 tokens so it doesn't flood your agent's context; ?truncateToolResult=false turns that off. Clients that already use code mode can add ?codemode=false to get one tool per API endpoint, which uses far more context. Some Cloudflare features need a paid plan. It also serves Cloudflare's agent skills (Wrangler, Durable Objects, the Agents SDK and Workers best practices) to agents that support MCP skills.