Deploy and manage MCP (Model Context Protocol) servers on Cloudflare Workers
mcp-deploy exposes 14 tools with HTTP transport and reasonable parameter schemas. Most tools have descriptions (10-150 chars), but many are terse and lack actionable context for LLM selection. Parameter schemas are present but inconsistently detailed, some tools (deployMcp, updateSecrets) have rich object parameters with minimal inline documentation. No output schemas are documented, forcing LLMs to infer response structure. Error handling is absent from visible code; no recovery guidance or categorization. Tool naming follows verb_noun convention (addMcp, deployMcp, removeMcp) but lacks clarity on destructive vs. reversible operations in names alone. Security concern: secrets are passed as object parameters rather than server-side injection.
Add a new MCP from a GitHub repository
Explicitly check for updates on GitHub for MCPs
Check the health status of a deployed MCP worker
Deploy an MCP to Cloudflare Workers with authentication configuration
Get the current Cloudflare login status and account information
Get metadata for a specific MCP including deployment status, secrets, and configuration
Get the list of configured secret keys for an MCP
List all MCPs in the registry with their deployment status
No output schemas documented. LLMs cannot infer response structure for any tool, forcing them to guess what fields are returned and risk downstream tool call failures.
Secrets passed as object parameters (deployMcp.secrets, updateSecrets.secrets) instead of server-side injection. Secrets will appear in agent logs and traces, creating compliance and security risks.
Destructive operations (removeMcp, undeployMcp) lack confirmation or dry-run support. No error handling visible to guide LLM recovery. Agents could accidentally delete MCPs without safeguards.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | <=2025-11-25 | v2 |
Remove an MCP from the registry and delete the Cloudflare worker
Setup Cloudflare authentication by triggering wrangler login
Test a connection to an external service using a test specification
Undeploy an MCP - delete the Cloudflare worker but keep the MCP in the registry
Update secrets on the deployed worker without redeploying
Validate a GitHub repository has proper MCP releases and metadata
Descriptions are terse (50-65 chars average) and lack context for LLM selection. E.g., 'Update secrets on the deployed worker without redeploying' does not explain when to use updateSecrets vs. deployMcp with new secrets.
Parameter descriptions missing or minimal. E.g., deployMcp.config and deployMcp.secrets are bare 'object' types with no guidance on expected keys, structure, or constraints. LLMs cannot construct valid payloads.