Remote MCP Server on Cloudflare

What is Remote MCP Server on Cloudflare?

A reference implementation for running a remote Model Context Protocol (MCP) server on Cloudflare Workers, complete with OAuth login. It targets developers who want to host MCP tools on Cloudflare’s edge infrastructure.

How to use Remote MCP Server on Cloudflare?

Clone the repository, install dependencies with npm install, and run locally with npx nx dev remote-mcp-server. Deploy to production by creating a KV namespace with npx wrangler kv namespace create OAUTH_KV, updating wrangler.jsonc, and running npm run deploy. Connect clients like the MCP Inspector or Claude Desktop by pointing them to the server’s SSE endpoint.

Key features of Remote MCP Server on Cloudflare

• Run MCP servers on Cloudflare Workers with OAuth login.
• Develop and test MCP servers locally before deploying.
• Connect to MCP Inspector for tool discovery and testing.
• Configure Claude Desktop via the mcp-remote proxy.
• Deploy to a public workers.dev URL instantly.
• Uses Cloudflare KV for OAuth state storage.

Use cases of Remote MCP Server on Cloudflare

• Host custom MCP tools on a globally distributed serverless platform.
• Prototype and demo MCP servers locally before production deployment.
• Provide MCP tools to remote AI assistants like Claude Desktop.
• Securely expose MCP servers with OAuth-based login flows.

FAQ from Remote MCP Server on Cloudflare

What dependencies or runtime are required?

Node.js and npm are needed to install dependencies and run local development commands. No additional tools beyond the Cloudflare Workers CLI (wrangler) are required for deployment.

How do I connect Claude Desktop to this server?

Add a configuration entry to Claude Desktop’s mcpServers section using the mcp-remote command and point args to the server’s SSE URL (e.g., https://worker-name.account-name.workers.dev/sse).

Where does OAuth session data live?

OAuth state is stored in a Cloudflare KV namespace (OAUTH_KV). You must create this namespace before deploying.

What transport does the server use?

The server uses SSE (Server-Sent Events) as its transport protocol. Clients connect to the /sse endpoint.

How can I debug connection issues?

Try connecting directly with npx mcp-remote http://localhost:8787/sse (local) or use the MCP Inspector. If needed, clear OAuth cached files in ~/.mcp-auth with rm -rf ~/.mcp-auth.