Remote MCP Server on Cloudflare

What is Remote MCP Server on Cloudflare?

Remote MCP Server on Cloudflare is a starter template that deploys a Model Context Protocol (MCP) server on Cloudflare Workers with OAuth login. It is designed for developers who need a remotely accessible MCP server that clients can connect to over the internet.

How to use Remote MCP Server on Cloudflare?

Clone the repository, install dependencies with npm install, and run locally using npx nx dev remote-mcp-server. For production, create a KV namespace with npx wrangler kv namespace create OAUTH_KV, add the namespace ID to wrangler.jsonc, then deploy with npm run deploy. Connect clients (MCP Inspector, Claude Desktop) to the /sse endpoint.

Key features of Remote MCP Server on Cloudflare

• OAuth login via browser for authentication.
• Local development with hot-reload via npx nx dev.
• Deploy to Cloudflare Workers with one command.
• Uses SSE transport for MCP communication.
• Compatible with MCP Inspector and Claude Desktop.
• Includes a local proxy (mcp-remote) for Claude Desktop.

Use cases of Remote MCP Server on Cloudflare

• Host a custom MCP server accessible from any remote client.
• Integrate MCP tools with Claude Desktop over the internet.
• Test and debug MCP servers locally before deploying to production.
• Provide OAuth‑protected MCP endpoints for team collaboration.

FAQ from Remote MCP Server on Cloudflare

What transport does the server use?

The server uses Server‑Sent Events (SSE) for MCP communication. Clients connect to the /sse endpoint.

What dependencies are required to run this server?

You need Node.js, npm, a Cloudflare account, and the Workers CLI (wrangler). The server also requires a Cloudflare KV namespace (OAUTH_KV).

How is user authentication handled?

Authentication is handled via OAuth login. When connecting from a client, a browser window opens for the user to log in with an email and password (locally, any credentials are accepted).

Where are session data and credentials stored?

OAuth session data is stored in the Cloudflare KV namespace (OAUTH_KV) that you create during deployment. Local auth files may be cached in ~/.mcp-auth.

How can I debug connection issues?

You can test connectivity directly using npx mcp-remote http://localhost:8787/sse (or your deployed URL). If problems persist, restart Claude Desktop or clear the auth cache with rm -rf ~/.mcp-auth.