Remote MCP Server on Cloudflare

What is Remote MCP Server on Cloudflare?

A remote MCP server that runs on Cloudflare Workers, complete with OAuth login, designed for developers who want to deploy and connect MCP tools over HTTP.

How to use Remote MCP Server on Cloudflare?

Clone the repository, install dependencies, and run locally with npx nx dev remote-mcp-server. Connect MCP Inspector or Claude Desktop using the SSE endpoint (e.g., http://localhost:8787/sse locally or the workers.dev URL after deployment).

Key features of Remote MCP Server on Cloudflare

• Deploy MCP servers on Cloudflare Workers.
• OAuth-based login for secure access.
• Supports SSE transport for remote clients.
• Local development with MCP Inspector.
• Direct integration with Claude Desktop.
• Uses Cloudflare KV for OAuth state.

Use cases of Remote MCP Server on Cloudflare

• Deploy a math tool server and call it from Claude Desktop.
• Create a remote MCP server with authentication for team use.
• Test and debug MCP tools locally before deploying to production.
• Connect any MCP client (Inspector, Claude) to a server on Cloudflare.

FAQ from Remote MCP Server on Cloudflare

What runtime or dependencies are required?

Node.js and npm are needed for local development. For deployment, a Cloudflare account and Wrangler CLI are required. Cloudflare KV is used for OAuth.

How does authentication work?

The server uses OAuth login. During development, a mock login screen accepts any email/password. After deployment, OAuth is handled by Cloudflare Workers.

What transport protocol does the server use?

All communication uses SSE (Server-Sent Events) over HTTP. The MCP inspector and Claude Desktop connect via an SSE URL.

How do I deploy the server?

Run npx wrangler kv namespace create OAUTH_KV, add the KV namespace ID to wrangler.jsonc, then deploy with npm run deploy. The server is available at a workers.dev URL.

Where are OAuth session data stored?

OAuth data is stored in Cloudflare KV, which is configured during deployment. Local auth files may be cleared from ~/.mcp-auth for debugging.