stellar

This MCP server is a Cloudflare Workers-based remote MCP instance that does not require authentication. It shows how to expose a set of tools to clients via the MCP protocol and how to connect external clients (like the Cloudflare AI Playground or Claude Desktop) to the remote server. To customize, you add individual tools inside the init() method of src/index.ts using this.server.tool(...). Once deployed, you can access the server's tools through the provided SSE endpoint and interact with them using the MCP protocol in client applications such as the AI Playground or Claude Desktop. For remote access from Claude Desktop, you configure the mcp-remote proxy to point at your remote server URL, enabling tools to appear in the Claude UI as available MCP tools.

Prerequisites:

• Node.js and npm installed on your machine
• Access to deploy Cloudflare Workers (via the example template)

Installation steps:

1. Create the MCP server from the Cloudflare template: npm create cloudflare@latest -- my-mcp-server --template=cloudflare/ai/demos/remote-mcp-authless

2. Change directory into your new project: cd my-mcp-server

3. Install dependencies: npm install

4. Build or publish the Worker (as per Cloudflare workflow) and deploy to Cloudflare Workers using your preferred method (e.g., wrangler publish) as documented in the template instructions.

5. Once deployed, note the SSE URL (e.g., https://your-deployed-url/sse) to use in MCP client configurations (as shown in the example mcp-remote setup).

6. Optional: to connect Claude Desktop, configure the mcp-remote proxy with the SSE URL so the tools become available in your local client.

Tips and notes:

• This example demonstrates an authless remote MCP server suitable for experimentation; for production, consider enabling appropriate authentication and access controls.
• Tools are added in the init() method of src/index.ts via this.server.tool(...); you can customize by defining each tool's behavior and capabilities there.
• When connecting from clients like Claude Desktop or the Cloudflare AI Playground, use the provided SSE URL for your deployed server. If you deploy to a different account or region, update the URL accordingly.
• If you encounter CORS or connection issues, verify that the deployed Worker is reachable at the SSE endpoint and that the client is configured to point to the exact /sse path.
• The example shows a remote mcp-remote proxy usage; replace the placeholder account URL with your actual deployed URL.
• The project may not produce a local server executable; instead, it runs as a Cloudflare Worker that serves the MCP protocol endpoints.