Remote

Provides remote MCP tools exposed via SSE over Cloudflare Workers and supports client connections from playgrounds and desktop clients.

typescript

0

GitHub Stars

typescript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

You can run a remote MCP server on Cloudflare Workers that exposes its tools over SSE and connect from various MCP clients. This makes your tooling available remotely, without requiring client-side authentication, and lets you extend the server by adding tools in code.

How to use

Once your remote MCP server is deployed, you can access its tools from an MCP client or from compatible playgrounds. Use the Cloudflare AI Playground to run your server as a remote MCP client: open the Playground, enter your deployed server URL, and start using the tools directly from the playground.

You can also connect to your remote MCP server from local clients by using the mcp-remote proxy. In Claude Desktop, configure the MCP server entry to point to the server SSE URL so the tools become available in Claude. This enables you to run your remote tools from your familiar desktop environment.

How to install

Prerequisites you need before starting:

Node.js and npm installed on your machine
Access to a Cloudflare account for deploying workers (recommended)
A text editor to modify server source files

Step 1. Deploy the remote MCP server to Cloudflare

npm create cloudflare@latest -- my-mcp-server --template=cloudflare/ai/demos/remote-mcp-authless

# Alternatively, you can deploy via the Cloudflare Workers deployment URL:
# https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/ai/tree/main/demos/remote-mcp-authless

Step 2. Customize your MCP server to expose your tools

// Inside src/index.ts
this.server.tool(/* define your tool here */)

Additional sections

Notes and practical guidance you can apply right away:

The remote server URL you deploy will be used by clients to connect. For example, a deployed URL may look like remote-mcp-server-authless.your-account.workers.dev/sse.
To test tool availability from a desktop client, configure the client to point at the server SSE URL and ensure the client reconnects after deployment changes.
If you prefer a local testing setup, you can connect Claude Desktop to the remote server by providing the remote SSE URL in the configuration, allowing you to verify tool availability without additional client software changes.