Remote MCP Server on Cloudflare

What is Remote MCP Server on Cloudflare?

This guide helps you set up a remote MCP (Model Context Protocol) server running on Cloudflare Workers with OAuth login for secure, remote tool calling.

How to use Remote MCP Server on Cloudflare?

Clone the repository, install dependencies, and run locally with npx nx dev remote-mcp-server. For production, deploy to Cloudflare Workers using npm run deploy. Connect clients via SSE endpoint (/sse) using the MCP Inspector or configure Claude Desktop with npx mcp-remote.

Key features of Remote MCP Server on Cloudflare

• Run MCP server on Cloudflare Workers for remote access
• OAuth login for secure authentication
• Compatible with MCP Inspector for local testing
• Full integration with Claude Desktop via local proxy
• Simple one-command deploy process

Use cases of Remote MCP Server on Cloudflare

• Expose MCP tools to remote AI clients like Claude Desktop
• Develop and test MCP servers locally before deploying
• Provide secure, authenticated tool access over the internet
• Enable distributed teams to share MCP resources

FAQ from Remote MCP Server on Cloudflare

What runtime/dependencies does the server require?

Node.js and npm are needed for local development. The deployed server runs on Cloudflare Workers using the Workers runtime.

How does authentication work?

OAuth login is built in with a mock login screen for local development. In production, you configure OAuth via Cloudflare Workers.

Where does server data live?

Local state (e.g., auth tokens) is stored in ~/.mcp-auth on the client machine. Server-side session data uses Cloudflare KV (OAUTH_KV).

What transport does the server use?

The server communicates via SSE (Server-Sent Events) over HTTP. Clients connect to the /sse endpoint.

Are there known limitations?

The README notes debugging steps: restarting Claude or clearing ~/.mcp-auth may help if problems occur. No other limitations are stated.