mcp-server-cloudflare
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_cloudflare_documentationA | Search the Cloudflare documentation. |
| migrate_pages_to_workers_guideA | ALWAYS read this guide before migrating Pages projects to Workers. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| workers-prompt-full | Detailed prompt for generating Cloudflare Workers code (and other developer platform products) from https://developers.cloudflare.com/workers/prompt.txt |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one for general documentation search and one specifically for migrating Pages to Workers. There is no overlap.
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.
With only 2 tools, the server feels very thin for the broad domain of Cloudflare products. It likely needs more tools to be useful.
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.