Skip to main content
Glama
cloudflare

mcp-server-cloudflare

Official
by cloudflare

Cloudflare MCP Server

Model Context Protocol (MCP) is a new, standardized protocol for managing context between large language models (LLMs) and external systems. In this repository, you can find several MCP servers allowing you to connect to Cloudflare's service from an MCP client (e.g. Cursor, Claude) and use natural language to accomplish tasks through your Cloudflare account.

These MCP servers allow your MCP Client to read configurations from your account, process information, make suggestions based on data, and even make those suggested changes for you. All of these actions can happen across Cloudflare's many services including application development, security and performance.

Every server in this repository exposes the same stateless Streamable HTTP handler at /mcp and /sse through a fresh SDK v2 server factory. /sse remains as a URL compatibility alias; it does not use the deprecated HTTP+SSE transport. A legacy SSE GET /sse request receives a 410 Gone Problem Details response with two migration options: configure the existing URL to use Streamable HTTP, or switch to the recommended /mcp URL for future compatibility. Modern 2026 requests and stateless 2025 requests share the same request-scoped implementation without an MCP protocol session. OAuth, credentials, account selection, application caches, and product Durable Objects remain application/security state where required.

Cloudflare offers the following MCP servers. The domain-specific servers are included in this repository, while the recommended Code Mode server is maintained in cloudflare/mcp:

Server Name

Description

Server URL

Code Mode server (recommended)

Best when you want broad access across Cloudflare's APIs through code execution

https://mcp.cloudflare.com/mcp

Documentation server

Get up-to-date reference information on Cloudflare

https://docs.mcp.cloudflare.com/mcp

Workers Bindings server

Build Workers applications with storage, AI, and compute primitives

https://bindings.mcp.cloudflare.com/mcp

Workers Builds server

Get insights and manage your Cloudflare Workers Builds

https://builds.mcp.cloudflare.com/mcp

Observability server

Debug and get insight into your application's logs and analytics

https://observability.mcp.cloudflare.com/mcp

Container server

Spin up a sandbox development environment

https://containers.mcp.cloudflare.com/mcp

Browser Run server

Fetch web pages, convert them to markdown and take screenshots

https://browser.mcp.cloudflare.com/mcp

Logpush server

Get quick summaries for Logpush job health

https://logs.mcp.cloudflare.com/mcp

AI Gateway server

Search your logs, get details about the prompts and responses

https://ai-gateway.mcp.cloudflare.com/mcp

AutoRAG server

Search and query account AutoRAG instances

https://autorag.mcp.cloudflare.com/mcp

Audit Logs server

Query audit logs and generate reports for review

https://auditlogs.mcp.cloudflare.com/mcp

DNS Analytics server

Optimize DNS performance and debug issues based on current setup

https://dns-analytics.mcp.cloudflare.com/mcp

Digital Experience Monitoring server

Get quick insight on critical applications for your organization

https://dex.mcp.cloudflare.com/mcp

Cloudflare One CASB server

Quickly identify any security misconfigurations for SaaS applications to safeguard users & data

https://casb.mcp.cloudflare.com/mcp

Radar server

Explore Cloudflare Radar internet insights

https://radar.mcp.cloudflare.com/mcp

Cloudflare Blog server

Search and read posts from the Cloudflare Blog

https://blog.mcp.cloudflare.com/mcp

Demo Day server

Demonstrate a minimal Cloudflare MCP server

https://demo-day.mcp.cloudflare.com/mcp

Which Cloudflare MCP server should you use?

Cloudflare provides two categories of MCP servers:

  • Code Mode server (mcp.cloudflare.com) in cloudflare/mcp: best when you want broad access across Cloudflare's APIs through code execution.

  • Domain-specific servers (*.mcp.cloudflare.com) in this repository: best when you want curated, typed tools for a specific Cloudflare product area.

When should you use each?

Use the Code Mode server when:

  • you need broad API coverage across many Cloudflare products

  • you prefer a smaller set of general-purpose tools

  • your workflow is better served by code execution

Use the domain-specific servers in this repository when:

  • you want purpose-built tools for a specific product area

  • you want more guided, typed interactions

  • you are working primarily within one Cloudflare domain such as observability, bindings, Radar, or Browser Run

Learn more about the Code Mode server here: cloudflare/mcp.

Related MCP server: Cloudflare MCP Server

Connect to an MCP server

Connect any MCP client with remote-server support directly to a URL in the table above. Cloudflare AI Playground also accepts server URLs in its interface.

Using Cloudflare's MCP servers from the OpenAI Responses API

To use one of Cloudflare's MCP servers with OpenAI's responses API, you will need to provide the Responses API with an API token that has the scopes (permissions) required for that particular MCP server.

For example, to use the Browser Run MCP server with OpenAI, create an API token in the Cloudflare dashboard here, with the following permissions:

Need access to more Cloudflare tools?

We're continuing to add more functionality to this remote MCP server repo. If you'd like to leave feedback, file a bug or provide a feature request, please open an issue on this repository

Troubleshooting

"Claude's response was interrupted ... "

If you see this message, Claude likely hit its context-length limit and stopped mid-reply. This happens most often on servers that trigger many chained tool calls such as the observability server.

To reduce the chance of running in to this issue:

  • Try to be specific, keep your queries concise.

  • If a single request calls multiple tools, try to to break it into several smaller tool calls to keep the responses short.

Paid Features

Some features may require a paid Cloudflare Workers plan. Ensure your Cloudflare account has the necessary subscription level for the features you intend to use.

Contributing

Interested in contributing, and running this server locally? See CONTRIBUTING.md to get started.

Available Tools

2 tools
migrate_pages_to_workers_guideA
Read-only

ALWAYS read this guide before migrating Pages projects to Workers.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true; description adds no additional behavioral context beyond the instruction to read the guide, which is sufficient for a static document.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, front-loaded, no unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter guide without output schema, the description adequately conveys the tool's purpose and usage context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist, so schema coverage is 100%. Description does not need to add parameter details; baseline 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool is a guide to be read before migrating Pages to Workers, distinguishing it from the sibling search tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use the tool (before migration), though no alternatives or exclusions are discussed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_cloudflare_documentationA
Read-only

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.
	
ParametersJSON Schema
NameRequiredDescriptionDefault
queryYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultsYes

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations include readOnlyHint=true, so the read-only nature is known. The description adds that results are 'semantically similar chunks', which gives insight into the behavior. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two paragraphs; the first sentence is concise, but the product list in the second paragraph is lengthy. Could be more concise, but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, read-only search), the description covers purpose, usage, and return format. Output schema exists, so return values are explained elsewhere. Adequately complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It lists topics to search, implying the query is a search string, but adds no details about format, length, or constraints. With only one parameter, it's minimally acceptable.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Search the Cloudflare documentation' and lists many product areas. The verb 'search' and resource 'Cloudflare documentation' are specific. The sibling tool 'migrate_pages_to_workers_guide' is clearly different, so no confusion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says it 'should be used to answer any question about Cloudflare products or features', providing clear usage context. It does not explicitly exclude cases where more specific tools might be better, but given only one sibling, it's adequate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv1.0.4
    • Changedmigrate_pages_to_workers_guide1 field changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • Changedsearch_cloudflare_documentation2 fields changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
      • changedOutput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. 1 tool updatev1.0.3
    • Changedsearch_cloudflare_documentation1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
        +  "$schema": "http://json-schema.org/draft-07/schema#",
        +  "additionalProperties": false,
        +  "properties": {
        +    "results": {
        +      "items": {
        +        "additionalProperties": false,
        +        "properties": {
        +          "id": {
        +            "description": "Source file ID",
        +            "type": "string"
        +          },
        +          "similarity": {
        +            "description": "Similarity score from AI Search",
        +            "type": "number"
        +          },
        +          "text": {
        +            "description": "Matching documentation chunk text",
        +            "type": "string"
        +          },
        +          "title": {
        +            "description": "Documentation page title",
        +            "type": "string"
        +          },
        +          "url": {
        +            "description": "Developer documentation URL",
        +            "type": "string"
        +          }
        +        },
        +        "required": [
        +          "similarity",
        +          "id",
        +          "url",
        +          "title",
        +          "text"
        +        ],
        +        "type": "object"
        +      },
        +      "type": "array"
        +    }
        +  },
        +  "required": [
        +    "results"
        +  ],
        +  "type": "object"
        +}
  3. 2 tool updatesv1.0.2
    • Changedmigrate_pages_to_workers_guide1 field changed
      • removedInput schema / additionalProperties
        Removed value: -false
    • Changedsearch_cloudflare_documentation1 field changed
      • removedInput schema / additionalProperties
        Removed value: -false
  4. 2 tool updates
    • First observedmigrate_pages_to_workers_guide
    • First observedsearch_cloudflare_documentation

TDQS

A3.9/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: one for general documentation search and one specifically for migrating Pages to Workers. There is no overlap.

Naming Consistency4/5

Both tool names follow a verb_noun pattern in snake_case, with 'search_cloudflare_documentation' and 'migrate_pages_to_workers_guide', though the second is much longer.

Tool Count2/5

With only 2 tools, the server feels very thin for the broad domain of Cloudflare products. It likely needs more tools to be useful.

Completeness2/5

Only documentation search and a specific migration guide are provided. Many core Cloudflare operations (e.g., managing resources, troubleshooting) are missing, leading to significant gaps.

Maintenance

ActivityActive
ResponsivenessWithin a week

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    A token-efficient MCP server that provides access to the entire Cloudflare API (2500+ endpoints) using a code execution pattern, enabling natural language management of Cloudflare services.
    11
    810
    Apache 2.0
  • A
    license
    Not graded
    quality
    D
    maintenance
    A high-performance MCP server providing AI assistants with read-only access to the Cloudflare ecosystem. Query your entire Cloudflare infrastructure using natural language through Claude, Cursor, or any MCP-compatible client.
    5
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cloudflare/mcp-server-cloudflare'

If you have feedback or need assistance with the MCP directory API, please join our Discord server