Building a Remote MCP Server on Cloudflare (Without Auth)

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

This example provides a template to deploy a remote MCP server on Cloudflare Workers that does not require authentication. It is intended for developers who want to expose MCP tools over the internet without added access control.

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

Deploy the server using the "Deploy to Workers" button on the README 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. Custom tools can be added by editing the init() method in src/index.ts with this.server.tool(...).

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

• Deploy a remote MCP server on Cloudflare Workers.
• Does not require authentication.
• Uses SSE transport.
• Customizable with your own tools.
• One-click deployment from GitHub.

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

• Expose MCP tools to remote clients without managing authentication.
• Test MCP servers from the Cloudflare AI Playground.
• Connect Claude Desktop to a remote MCP server via the mcp-remote proxy.

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

What runtime does this server use?

It runs on Cloudflare Workers using the Workers runtime.

Does this server require authentication?

No, this example deploys a remote MCP server without authentication.

Where does my MCP code live?

Your tools and logic are defined in src/index.ts inside the server project.

What transport does this MCP server use?

It uses the SSE (Server-Sent Events) transport, accessible at the /sse endpoint.

Can I connect to it from local MCP clients like Claude Desktop?

Yes, use the mcp-remote proxy (available on npm) and configure the remote URL in Claude Desktop’s MCP settings.