mcp-cloud-deploy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOUDFLARE_API_TOKEN | Yes | Your Cloudflare API token with Pages Write permissions. For automatic DNS changes, also grant Zone:Read and DNS:Edit for the relevant zones. | |
| CLOUDFLARE_ACCOUNT_ID | Yes | The Cloudflare account ID that owns your Pages project and DNS zones. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deploy_to_cloudflare_pagesB | Deploy a static website to Cloudflare Pages. Supports landing pages with nested image/assets and React/Vite single-page apps. If domain is omitted, the deployment URL works without owning a domain; if provided, bind it and configure Cloudflare DNS when possible. |
| attach_custom_domainA | Bind a custom domain to a Cloudflare Pages project and create a CNAME in a matching Cloudflare DNS zone when available. |
| list_deploymentsC | List recent Cloudflare Pages deployments, live URLs, and custom domain bindings. Cloudflare Pages deployments support nested static assets and React/Vite builds. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools have largely distinct primary actions (deploy, bind domain, list deployments). However, deploy_to_cloudflare_pages explicitly also binds custom domains and configures DNS, which overlaps with attach_custom_domain and could make an agent unsure which to use when a domain is supplied at deploy time.
All names are snake_case with a leading verb (deploy_, attach_, list_) and target a Cloudflare Pages resource, giving a predictable pattern. deploy_to_cloudflare_pages is noticeably longer and adds a provider prefix the others omit, a minor deviation.
Three tools is thin for a deployment server; the lifecycle of a Pages project typically involves more operations. The narrow scope (deploy static site, bind domain, list) is defensible but borderline minimal.
Core flow of deploy → bind domain → list is covered, but there are notable gaps: no rollback/retry, no delete or remove-domain, no project listing or deletion, and no access to build logs or deployment status details. Agents hitting failures would have no recovery tools.