Cloud Platform★★★★4/5
CloudflareMCP
Cloudflare's official MCP server covers their entire developer platform: deploy Workers, manage KV namespaces, create and query D1 databases, handle R2 object storage, and configure Hyperdrive connections.
The OAuth authentication flow means you don't need to manage API tokens — just authenticate through the browser once. The server is remote-hosted, so there's nothing to install locally. Full CRUD operations across all services.
Most useful if you're already on the Cloudflare platform. If you're using Workers, KV, or D1 in your stack, this turns natural language into infrastructure changes.
Pros
- + Official Cloudflare project with OAuth authentication
- + Covers Workers, KV, R2, D1, and Hyperdrive
- + Remote hosted — no local setup needed
- + Full CRUD: deploy Workers, manage buckets, run SQL on D1
Cons
- - Some features require paid Workers plan
- - Uses SSE transport (being deprecated in favor of StreamableHTTP)
- - No value if you don't use the Cloudflare platform
How We Use It
nxsi.io runs behind Cloudflare — DNS, WAF, and a Cloudflare Tunnel that bridges the public site to the self-hosted analytics API. The MCP server handles DNS record management and tunnel configuration checks without leaving the Claude Code session.
The most common use case is verifying Cloudflare settings after infrastructure changes. When we set up the analytics tunnel (t.nxsi.io), debugging the path restrictions and DNS CNAME records involved a lot of back-and-forth between the Cloudflare dashboard and the terminal. With the MCP server, Claude can inspect the current DNS state, check tunnel routes, and verify configuration — all in the same conversation where it's writing the code.
cloudflareworkersserverlessedgeKVR2D1