cloudflare-mcp-server

Deploy MCP servers on Cloudflare Workers using production-ready templates that handle SSE and HTTP transport configuration automatically. This Skill catches URL path mismatches—the top reason MCP servers fail to connect—by validating base paths and ensuring startsWith matching against your exact deployed URL before testing.

Yes. This Skill includes OAuth-enabled templates and the @cloudflare/workers-oauth-provider integration to deploy GitHub-connected MCP servers. Pre-built scripts handle OAuth configuration, Durable Objects state management, and deployment validation so your server authenticates requests correctly on first deploy.

Run pre-deployment testing steps included in this Skill to validate URL paths, transport configuration, and McpAgent exports against your live Cloudflare Worker URL. Testing catches path mismatches and Durable Objects state issues locally, preventing 22+ common MCP deployment errors.

No. This Skill solves base-path and transport configuration problems automatically through templates and reference scripts. It handles SSE and Streamable HTTP transport setup, validates path accuracy with startsWith logic, and ensures Durable Objects and McpAgent exports match your deployed Worker URL.

URL path mismatches between configuration and deployed Worker endpoints are the primary cause. This Skill provides debugging tools and validation scripts to identify and fix path mismatches, ensuring your MCP server's base path exactly matches the Cloudflare Workers deployment URL.

This Skill's templates and reference implementations show correct Durable Objects initialization and McpAgent export patterns for Cloudflare Workers. Pre-deployment testing validates state handling and exports match your transport configuration, preventing runtime connection failures.