Building a Remote MCP Server on Cloudflare (Without Auth)

What is Building a Remote MCP Server on Cloudflare (Without Auth)?

This project lets you deploy a remote MCP server on Cloudflare Workers that requires no authentication. It is intended for developers who want a quick, publicly accessible MCP endpoint without implementing auth.

How to use Building a Remote MCP Server on Cloudflare (Without Auth)?

Deploy via the “Deploy to Workers” button or run npm create cloudflare@latest -- my-mcp-server --template=cloudflare/ai/demos/remote-mcp-authless. Customize tools inside src/index.ts using this.server.tool(...). Connect to the Cloudflare AI Playground by entering your deployed URL (<account>.workers.dev/sse). For local MCP clients like Claude Desktop, use the mcp-remote proxy pointing to the same SSE endpoint.

Key features of Building a Remote MCP Server on Cloudflare (Without Auth)

• One‑click deploy to Cloudflare Workers
• No authentication required
• Add custom tools via this.server.tool()
• Connects to Cloudflare AI Playground
• Works with local clients via mcp-remote proxy

Use cases of Building a Remote MCP Server on Cloudflare (Without Auth)

• Quickly prototyping MCP tools without setting up auth
• Serving MCP endpoints to remote AI agents (e.g., Cloudflare Playground)
• Integrating with Claude Desktop using the mcp‑remote proxy

FAQ from Building a Remote MCP Server on Cloudflare (Without Auth)

How do I deploy this server?

Use the “Deploy to Workers” button or run npm create cloudflare@latest with the provided template.

How do I add custom tools?

Define each tool inside the init() method of src/index.ts using this.server.tool(...). Refer to Cloudflare’s MCP tools documentation for details.

How do I connect to the Cloudflare AI Playground?

Go to https://playground.ai.cloudflare.com/, enter your deployed MCP server URL (<account>.workers.dev/sse), and start using the tools.

How do I connect to Claude Desktop?

Install the mcp-remote npm package, then add a configuration entry in Claude Desktop pointing to your server’s SSE URL (e.g., http://localhost:8787/sse or the remote URL).