remote -authless

This MCP server is a remote, authentication-free MCP instance deployed on Cloudflare Workers. It exposes a set of tools that clients can call via the MCP protocol without requiring user authentication. You can deploy the server using the Cloudflare template or via the npx-based remote tool, and then connect to it from clients such as the Cloudflare AI Playground or Claude Desktop using the provided remote URL. The server is designed to be extended by adding tools inside the init() method of src/index.ts, enabling you to define and expose custom capabilities for copilots or agents to invoke.

To use from a remote client like Claude Desktop, configure the client to point at the server’s SSE endpoint (for example remote-mcp-server-authless.your-account.workers.dev/sse). If you’re using the mcp-remote proxy, you can point the remote tool at your server URL to integrate it into local workflows. The Cloudflare AI Playground also provides a direct way to test the server by entering the deployed URL in the Playground connection flow and invoking the available tools directly from the UI.

Prerequisites:

• Node.js and npm installed on your machine
• A Cloudflare account if you plan to deploy to Workers
• Access to the repository or template referenced in the README

Install and deploy locally or to Cloudflare:

1. Create the MCP remote server using the template (as shown in the README):

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

2. Follow the prompts to configure the deployment and push to Cloudflare Workers (if deploying to Cloudflare). If you prefer a local remote endpoint, you can start from the template and run the server locally as needed, depending on how the template is set up in your environment.
3. Once deployed, note the SSE URL (for example, https://remote-mcp-server-authless.your-account.workers.dev/sse) that clients will use to connect.
4. To connect from Claude Desktop or other clients, reference the mcp-remote proxy tool and point it at the SSE URL as shown in the example configuration.

No additional build steps are required beyond what the template specifies; ensure you have network access to the deployed endpoint when testing from clients.

Tips and common issues:

• The remote-authless server does not require authentication, so ensure you control who can access the endpoint to avoid misuse.
• When adding custom tools, modify the init() method in src/index.ts and redeploy to include the new tools in the MCP server.
• If you encounter connection issues, verify the SSE URL is accessible from your network and that the deployment endpoint is correct (remote-mcp-server-authless.<your-account>.workers.dev/sse).
• For Claude Desktop integration, ensure your config matches the example: the args should point to the exact SSE URL of your deployed remote server.
• If you’re testing locally with the mcp-remote proxy, ensure the proxy is up to date and compatible with the remote server’s endpoint version.