Remote MCP Server on Cloudflare

@kartik71

About Remote MCP Server on Cloudflare

No overview available yet

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "guitar-remote-mcp-server": {
      "command": "npx",
      "args": [
        "nx",
        "dev",
        "remote-mcp-server"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Remote MCP Server on Cloudflare?

A template for deploying a remote MCP (Model Context Protocol) server on Cloudflare Workers with OAuth login. It provides a working example that can be run locally, connected to the MCP Inspector, and integrated with Claude Desktop over SSE transport.

How to use Remote MCP Server on Cloudflare?

Clone the repository, install dependencies with pnpm install, then run locally with npx nx dev remote-mcp-server. Connect using the MCP Inspector (set transport to SSE and URL to http://localhost:8787/sse) or configure Claude Desktop with mcp-remote pointing to the same URL. Deploy to Cloudflare by creating a KV namespace for OAuth and running npm run deploy.

Key features of Remote MCP Server on Cloudflare

Runs as a Cloudflare Worker with SSE transport
Includes OAuth login flow for authentication
Works with MCP Inspector for local testing
Integrates directly with Claude Desktop via mcp-remote proxy
Supports both local development and production deployment
Example math tool included for demonstration

Use cases of Remote MCP Server on Cloudflare

Prototype and test a remote MCP server locally before deploying
Connect Claude Desktop to a custom MCP server with OAuth security
Deploy a scalable serverless MCP backend on Cloudflare’s edge network
Demonstrate MCP tool calling with a simple arithmetic tool

FAQ from Remote MCP Server on Cloudflare

What is the difference between local development and production deployment?

Local development uses http://localhost:8787/sse and a mock login. Production deploys to a workers.dev URL with real OAuth authentication (requires an OAUTH_KV namespace).

What dependencies or runtime are required?

Node.js and pnpm (not npm) are required. For local development, use pnpm install and npx commands. The server itself runs on Cloudflare Workers.

How does authentication work?

The server includes an OAuth login page. Locally, a mock user/password screen appears. In production, Cloudflare Workers handle the OAuth flow with a KV store (OAUTH_KV) for session data.

Which transport is used?

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

Can I clear cached authentication data?

Yes, if OAuth issues arise, you can delete local auth files by running rm -rf ~/.mcp-auth and restarting Claude Desktop.

Frequently asked questions

What is the difference between local development and production deployment?

Local development uses `http://localhost:8787/sse` and a mock login. Production deploys to a `workers.dev` URL with real OAuth authentication (requires an OAUTH_KV namespace).

What dependencies or runtime are required?

Node.js and pnpm (not npm) are required. For local development, use `pnpm install` and `npx` commands. The server itself runs on Cloudflare Workers.

How does authentication work?

The server includes an OAuth login page. Locally, a mock user/password screen appears. In production, Cloudflare Workers handle the OAuth flow with a KV store (OAUTH_KV) for session data.

Which transport is used?

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

Can I clear cached authentication data?

Yes, if OAuth issues arise, you can delete local auth files by running `rm -rf ~/.mcp-auth` and restarting Claude Desktop.

Comments

Basic information

More Cloud & Infrastructure MCP servers

Nippy

Nippy is drag-and-drop hosting (nippy.host) with an MCP server: connect it and your assistant can publish HTML, folders of photos, or file downloads to a live *.nippy.site URL — and keep editing the site in place at the