Remote Cloudflare

You run a remote MCP server on Cloudflare Workers that you can connect to from MCP clients or local tools. This server lets you expose predefined tools and interact with them remotely, enabling you to delegate tasks from any client that supports MCP.

How to use

You can connect to your remote MCP server from MCP clients or local proxies. Use the HTTP endpoint when your client supports remote servers over HTTP, or use a local proxy command to bridge to the remote server from your desktop client.

How to install

Prerequisites you need on your machine before starting:

Step-by-step options you can follow now:

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

Additional notes

To customize your MCP server, add your own tools inside the init() method of the server source using this.server.tool(...) so they are available to clients.

Connect to the server from the Cloudflare AI Playground to experiment with your MCP tools in a remote client environment.

You can also connect from local MCP clients by using the mcp-remote proxy. The configuration example shows how Claude Desktop can be wired to your remote MCP server and expose its tools locally. Use the remote URL for the server in the proxy configuration.

MCP connection configurations

Two explicit ways to connect to the remote server are provided here. The first uses an HTTP URL directly from an MCP client. The second uses a local proxy (stdio) approach to connect from a desktop client like Claude.

{
  "mcpServers": {
    "remote_authless": {
      "type": "http",
      "url": "https://remote-mcp-server-authless.<your-account>.workers.dev/sse",
      "args": []
    }
  }
}

Connecting via a local proxy from a desktop client

If you prefer to connect through a local proxy, you can run a command that bridges to the remote server. The example below shows how to configure a local proxy invocation to point at the remote server.

{
  "mcpServers": {
    "remote_authless_proxy": {
      "type": "stdio",
      "name": "remote_authless_proxy",
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://remote-mcp-server-authless.<your-account>.workers.dev/sse"
      ]
    }
  }
}

Security considerations

Because this example enables an authless remote MCP server, treat it as publicly accessible and ensure you only expose it to trusted environments. Consider rotating access controls and using network-level protections where possible.

Troubleshooting

If you cannot connect, verify that the remote URL is reachable from your network and that your MCP client is configured to talk to the correct endpoint. If you are using the local proxy, ensure the proxy tool is installed and that the URL you point to ends with /sse.