Pandaw

This MCP server lets you run a remote MCP (Multi-Client Prompt) server that can be accessed over HTTP or run locally via a stdio-based proxy. It’s useful for hosting your own MCP tools and connecting from clients like the Cloudflare AI Playground or Claude Desktop without needing authentication in certain setups.

How to use

You can access your MCP server from any compatible MCP client. Deploy it to Cloudflare Workers to get an online URL you can point clients at, or run a local stdio proxy to connect to tools from another machine. For example, you can use the Cloudflare AI Playground to experiment with your tools by providing your deployed server’s URL. You can also connect Claude Desktop to your server by configuring the mcpServers entry to point to your local or remote server.

How to install

Prerequisites you need before starting:

• Node.js and npm installed on your machine.

• Access to a Cloudflare account if you plan to deploy to Cloudflare Workers.

How to install

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

How to use locally and remotely

The remote MCP server can be accessed without auth in this example setup, and you can customize the tools by editing the init() method in your source to register each tool with this.server.tool(...). When you’re ready, you can connect your clients via the URL created by the deployment process or run a local proxy to connect from a development machine.

Additional notes

Connect to the Cloudflare AI Playground to experiment with your MCP server. Open the Playground, enter your deployed server URL, and start using your MCP tools directly from the playground.

Claude Desktop configuration example

You can connect to your remote MCP server from Claude Desktop by editing the client configuration. Use the following as a starting point in Claude Desktop under Settings > Developer > Edit Config.

Claude Desktop configuration example

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

Troubleshooting and notes

If you encounter connectivity issues, verify the server URL is correct and that the target port or path (for example /sse) is reachable. When running locally, ensure the stdio proxy is started with the proper command, and that any required environment variables are set if your tools rely on them.

Security considerations

This setup demonstrates an authless remote MCP server for demonstration purposes. In production, consider enabling authentication and access controls to protect your tools and data. Review your deployment and proxy configuration to enforce secure access where needed.