Home Catalog Cloudflare Docs

Cloudflare Docs

Developer tools Listed by MCPBay

Search the official Cloudflare developer documentation: Workers, Pages, R2, D1, Zero Trust and more

By: Cloudflare

The MCPBay team added this server to the catalog. Its author is not affiliated with MCPBay and did not submit it here. The server runs on the author's side, so MCPBay has no call statistics for it.
Connect

The connection URL lives in your cabinet. Use "Add" above, then open "My MCPs" — the address for your AI client appears there.

About

Cloudflare's documentation MCP server gives an assistant up-to-date answers about the Cloudflare developer platform straight from the official docs.

Tools:
- search_cloudflare_documentation — semantic search across Cloudflare documentation (Workers, Pages, R2, D1, KV, Durable Objects, Queues, AI, DNS, Zero Trust and others), returning the relevant passages.
- migrate_pages_to_workers_guide — a step-by-step guide for moving a Cloudflare Pages project to Workers.

Typical use: "How do I bind an R2 bucket to a Worker and stream an upload to it?" — the assistant answers from the current docs instead of outdated examples.

Who it is for: developers building on Cloudflare.

Notes: free, no Cloudflare account needed — it only reads public documentation. Cloudflare publishes separate, sign-in servers for managing your own account (Workers bindings, observability, and others).

Tools (2)

  • migrate_pages_to_workers_guide

    ALWAYS read this guide before migrating Pages projects to Workers.

  • search_cloudflare_documentation

    Search the Cloudflare documentation. This tool should be used to answer any question about Cloudflare products or features, including: - Workers, Pages, R2, Images, Stream, D1, Durable Objects, KV, Workflows, Hyperdrive, Queues - AI Search, Workers AI, Vectorize, AI Gateway, Browser Run - Zero Trust, Access, Tunnel, Gateway, Browser Isolation, WARP, DDOS, Magic Transit, Magic WAN - CDN, Cache, DNS, Zaraz, Argo, Rulesets, Terraform, Account and Billing Results are returned as semantically similar chunks to the query.

Source Docs