Building a Remote MCP Server on Cloudflare (Without Auth)

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

This example deploys a remote MCP server on Cloudflare Workers that requires no authentication, using SSE transport. It is intended for developers who want a quick, auth‑free way to expose MCP tools over the internet.

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. After deployment, the server is available at a URL like remote-mcp-server-authless.<your-account>.workers.dev/sse. Customize tools inside src/index.ts using this.server.tool(...).

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

• Deployed on Cloudflare Workers – no server management
• No authentication required for this example
• Uses SSE (Server‑Sent Events) transport
• Customizable with your own MCP tools
• One‑click deploy via Cloudflare dashboard

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

• Expose MCP tools to remote clients without auth setup
• Quick prototyping or internal tooling
• Connect to Cloudflare AI Playground for testing
• Connect to Claude Desktop via 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 -- my-mcp-server --template=cloudflare/ai/demos/remote-mcp-authless.

How do I add custom tools?

Define each tool inside the init() method of src/index.ts using this.server.tool(...).

How can I connect to Cloudflare AI Playground?

Go to https://playground.ai.cloudflare.com/, enter your deployed MCP server URL (ending in /sse), and start using the tools.

Can I use this server with Claude Desktop?

Yes – use the mcp-remote proxy. Configure Claude Desktop’s MCP settings with npx mcp-remote <your-sse-url>.

What transport does this server use?

It uses SSE (Server‑Sent Events) over HTTPS. The client connects to the /sse endpoint.