Skip to content

Development integration

Cloudflare Docs MCP server for Claude, Codex and Cursor

Search up-to-date Cloudflare developer documentation. Connect the Cloudflare MCP server to Toolstile once, then choose which of its tools Claude Code, Codex, Cursor and Claude Desktop may use.

Free plan available. Server credentials stay in Toolstile, not in agent configs.

On this page

What your AI apps can do with Cloudflare Docs

  • Search Cloudflare documentation
  • Get migration guidance

Cloudflare Docs MCP tools

2 tools and 1 prompt, listed by Toolstile from the server itself on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.

ToolWhat it doesSuggested rule
search_cloudflare_documentationSearch the Cloudflare documentation.Allow (read-only)
migrate_pages_to_workers_guideALWAYS read this guide before migrating Pages projects to Workers.Allow (read-only)

Cloudflare Docs MCP prompts

  • workers-prompt-full: Detailed prompt for generating Cloudflare Workers code (and other developer platform products) from https://developers.cloudflare.com/workers/prompt.txt

Suggested access for each AI app

  • 2 tools marked read-only (search_cloudflare_documentation, migrate_pages_to_workers_guide). These are usually safe to allow.

These are hints the server reports about its own tools, not guarantees.

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Cloudflare Docs connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

  1. Connect once. Add Cloudflare Docs to a workspace (no sign-in). Toolstile keeps the credential, so no agent config holds it.
  2. Choose access per app. Give Claude Code every Cloudflare Docs tool, give Cursor only the read tools, or keep Cloudflare Docs away from an app entirely.
  3. Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
  4. Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the Cloudflare Docs MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

Shell
claude mcp add --transport http toolstile 'https://toolstile.com/mcp'

Then connect Cloudflare Docs in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the Cloudflare endpoint to each app separately. In Claude Code:

Shell
claude mcp add --transport http cloudflare-docs 'https://docs.mcp.cloudflare.com/mcp'

In Cursor's mcp.json:

JSON
{
  "mcpServers": {
    "cloudflare-docs": {
      "url": "https://docs.mcp.cloudflare.com/mcp"
    }
  }
}

Some servers accept only clients they have approved, or need a token header. Check the Cloudflare MCP documentation for what your client needs.

Before you connect

No account needed.

Server details

DetailValue
PublisherCloudflare
Endpointhttps://docs.mcp.cloudflare.com/mcp
AuthenticationNo sign-in
CategoriesDevelopment
Tool list2 tools, observed 29 October 2026 (discovery)

Cloudflare MCP documentation