Remote MCP Server on Cloudflare

What is Remote MCP Server on Cloudflare?

A template for running a remote MCP (Model Context Protocol) server on Cloudflare Workers with OAuth login. It provides the infrastructure to deploy MCP tools that can be accessed remotely and authenticated, intended for developers building AI agent tooling.

How to use Remote MCP Server on Cloudflare?

Clone the repository, install dependencies with npm install, run locally with npx nx dev remote-mcp-server, deploy with npm run deploy. Connect using the MCP Inspector or Claude Desktop by configuring the SSE endpoint at <url>/sse.

Key features of Remote MCP Server on Cloudflare

• Runs on Cloudflare Workers with OAuth login
• Deployable with a single npm run deploy command
• Uses SSE transport for MCP communication
• Includes a KV namespace for OAuth state
• Works with MCP Inspector and Claude Desktop
• Supports local development with mock authentication

Use cases of Remote MCP Server on Cloudflare

• Hosting custom MCP tools accessible over the internet
• Prototyping MCP servers with OAuth-based authentication
• Connecting Claude Desktop to a remotely deployed tool server
• Testing MCP endpoints locally before production deployment

FAQ from Remote MCP Server on Cloudflare

How do I connect Claude Desktop to a deployed server?

Update the claude_desktop_config.json with mcp-remote pointing to your workers.dev URL followed by /sse, for example https://worker-name.account-name.workers.dev/sse.

What transport does the server use?

The server uses Server-Sent Events (SSE) transport, configured by connecting to the /sse endpoint.

How do I deploy my own version?

Create a KV namespace with npx wrangler kv namespace create OAUTH_KV, add the namespace ID to wrangler.jsonc, then run npm run deploy.

How can I debug connection issues?

Restart Claude, test the connection directly with npx mcp-remote http://localhost:8787/sse, or clear cached auth data with rm -rf ~/.mcp-auth.

What authentication method is used?

The server implements OAuth login. In local development a mock login screen accepts any email and password; in production the deployed Worker handles OAuth flows.