Remote

You can deploy a remote MCP (Magic Command Protocol) server that runs on Cloudflare Workers, enabling you to expose tools to MCP clients without requiring authentication. This setup lets you connect from playgrounds or local MCP clients and extend the server with your own tools for collaboration and automation.

How to use

Use an MCP client such as the Cloudflare AI Playground or a local MCP client to interact with your remote server. With an HTTP remote URL, you can call tools directly from the client and receive responses in real time. You can also connect traditional local clients via a proxy to access the remote server commands.

How to install

Prerequisites: you need Node.js and npm installed on your machine.

1. Create your remote MCP server project using the Cloudflare template.

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

How to customize your MCP server

To add your own tools to the MCP server, implement each tool inside the init() method of src/index.ts using this.server.tool(...).

Other important setup notes

You can connect to the Cloudflare AI Playground to test and run your MCP server. Use the deployed URL in the playground to access your tools directly.

If you want to connect Claude Desktop or other local MCP clients to your remote server, you can configure the mcp-remote proxy to point at your remote endpoint.

Example client configuration for Claude Desktop

{
  "mcpServers": {
    "calculator": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://localhost:8787/sse"  // or remote-mcp-server-authless.your-account.workers.dev/sse
      ]
    }
  }
}

Connect to Cloudflare AI Playground

Go to Cloudflare AI Playground and enter your deployed MCP server URL to start using your MCP tools directly from the playground.

Notes on security and access

This setup intentionally exposes tools via an authless remote endpoint. Treat it as suitable for experimentation or internal workflows. If you plan to expose sensitive tooling, consider enabling authentication and access controls.

Troubleshooting tips

• Verify the remote URL is reachable from your client.
• Ensure the Cloudflare Workers deployment is active and returning responses at /sse.
• Check that the tool definitions are correctly initialized in src/index.ts.
• Use the Cloudflare deployment CLI or UI logs to diagnose deployment errors.