cloudflare-remote

This MCP server provides a remote, Cloudflare Workers-based implementation of the Model Context Protocol with OAuth login support. When you run it locally, it starts a server that exposes an SSE endpoint at /sse for MCP clients to connect to and discover tools. Tools defined by the MCP server can be invoked from the MCP Inspector or from compatible clients like Claude Desktop once you configure the connection. The server is designed to be deployed to Cloudflare Workers and includes a workflow for OAuth-based authentication, so end users can sign in securely before interacting with tools.

To connect with the MCP Inspector, start the server locally (via the command in the mcp_config) and then in the Inspector choose SSE as the transport type and point it at http://localhost:8787/sse. After connecting, you’ll see a login screen mockup; provide credentials to authenticate and you’ll gain access to the available tools. This setup also supports deploying to Cloudflare and exposing the same /sse URL through a Worker, enabling remote clients to connect to your MCP server just like you did locally.

Prerequisites:

• Node.js and npm installed on your machine
• Git installed
• Optional: Cloudflare Wrangler for deployment

Install and run locally:

1. Clone the repository (as per the README example):

git clone git@github.com:cloudflare/ai.git

2. Install dependencies:

cd ai
npm install

3. Run the MCP server locally (using the workspace/NX setup mentioned in the README):

npx nx dev remote-mcp-server

4. Open http://localhost:8787/ to verify the local server is running.

Deploy to Cloudflare:

1. Ensure Cloudflare Wrangler is installed and configured.
2. Create the KV namespace for OAuth data:

npx wrangler kv namespace create OAUTH_KV

3. Follow the guidance to add the KV namespace ID to wrangler.jsonc (as described in the README).
4. Deploy:

npm run deploy

Notes:

• You may need to adjust environment variables for OAuth and Cloudflare interactions depending on your setup.
• The server exposes /sse for MCP client connections and expects authentication via the OAuth flow configured in Cloudflare Workers.

Tips and common issues:

• After deploying, ensure the OAuth KV namespace is correctly configured in wrangler.jsonc and that any client credentials are set in your environment if required by the OAuth flow.
• If you encounter authentication problems, you can reset local credentials by removing the MCP auth data at ~/.mcp-auth as suggested in the README:

rm -rf ~/.mcp-auth

• When testing locally, the MCP Inspector is the recommended tool to explore and call defined tools. Ensure you switch the Inspector transport to SSE and point it to http://localhost:8787/sse.
• For Claude Desktop integration, you typically set up the mcp-remote proxy (via npx mcp-remote http://localhost:8787/sse) and configure Claude to point to the generated workers.dev URL after deployment.