Remote

This MCP server runs on Cloudflare Workers and provides remote tools that you can access from MCP clients. It supports connecting through a remote HTTP SSE endpoint or via a local stdio proxy, enabling you to run and manage tools without hosting them locally.

How to use

You can use this MCP server from an MCP client or through tools that connect to an MCP endpoint. Two primary connection methods are shown here: a remote HTTP SSE endpoint and a local stdio proxy. Use the HTTP method when you want to reach the server directly over the internet. Use the stdio method when you want to run the MCP tools through a local command and proxy to the remote server.

Connect to the remote server by pointing your MCP client to the HTTP URL of the server. The endpoint follows this pattern: remote-mcp-server-authless.<your-account>.workers.dev/sse. This URL is provided as the deployment example and can be used to access the server’s MCP endpoints from compatible clients.

If you prefer to run the server locally through a proxy, configure your client to use the stdio proxy command shown in the example. The setup uses a local command that proxies requests to the remote server: npx mcp-remote http://localhost:8787/sse or the remote URL alternative remote-mcp-server-authless.your-account.workers.dev/sse. This approach makes the MCP tools available to local clients like Claude Desktop or other MCP clients.

You can also deploy via a command line helper to create the remote MCP server on your machine or cloud environment. Run the following to initialize the remote server on Cloudflare Workers via the command line: npm create cloudflare@latest -- my-mcp-server --template=cloudflare/ai/demos/remote-mcp-authless

How to install

# Prerequisites
- Node.js (14+)
- npm (comes with Node.js)

# Install and create the remote MCP server on Cloudflare with the provided template
npm create cloudflare@latest -- my-mcp-server --template=cloudflare/ai/demos/remote-mcp-authless

The deployment creates a remote MCP server accessible at a URL similar to remote-mcp-server-authless.<your-account>.workers.dev/sse. You can then connect MCP clients to that URL to use the included tools.

If you want to run a local proxy for development and testing, you can use an existing local command that proxies to the remote SSE endpoint. The configuration example shows how Claude Desktop can be pointed to your remote server.

Additional sections

Customizing your MCP server: To add your own tools, define each tool inside the init() method of src/index.ts using this.server.tool(...). This enables you to extend the MCP server with your own capabilities and expose them to clients.

Connect to the Cloudflare AI Playground: You can connect your MCP server to the Cloudflare AI Playground to test and run tools from a remote MCP client. Open the Playground, enter the deployed MCP server URL (remote-mcp-server-authless.<your-account>.workers.dev/sse), and you can start using your MCP tools directly from the playground.

Claude Desktop integration: You can connect to your remote MCP server from Claude Desktop by adding a local proxy configuration. In Claude Desktop, go to Settings > Developer > Edit Config and include the remote server URL in the mcpServers section. This enables Claude to access the remote tools as if they were running locally.

Available tools

calculator

A proxy-enabled tool that routes MCP commands through the remote SSE endpoint using a local proxy configuration.

mcp-remote

Client-side proxy tool used to connect local environments to the remote MCP server via the SSE endpoint.