home / mcp / remote mcp server (cloudflare)
Provides a remote MCP server endpoint on Cloudflare Workers, enabling tool-based automation via HTTP/SSE without authentication.
Configuration
View docs{
"mcpServers": {
"assif83-remote-mcp-server-authless": {
"url": "https://remote-mcp-server-authless.<your-account>.workers.dev/sse"
}
}
}You can host a remote MCP server that runs on Cloudflare Workers and makes its capabilities available to MCP clients without requiring authentication. It lets you deploy simple, tool-enabled automation that you can connect to from playgrounds or local clients.
You connect to the remote MCP server from an MCP client or tool by pointing the client at the server’s SSE endpoint. Use the Cloudflare-hosted URL when you want a public-facing instance, or connect locally via a proxy when you test tools before deployment. Once connected, you can invoke your MCP tools from the client just like you would with any other MCP server, and you’ll receive responses that drive your workflows.
Prerequisites: install Node.js and npm so you can run the MCP setup commands.
1) Create the remote MCP server using the standard setup command.
2) Deploy to Cloudflare Workers using the provided template command so the server runs at a public URL.
3) Confirm the deployment URL is active and note the /sse endpoint for MCP clients.
You can customize your MCP server by adding tools in the initialization flow of the server code. Specifically, you add each tool inside the init() method using this.server.tool(...). This lets you expose new capabilities without changing client code.
Connect to the Cloudflare AI Playground to test your MCP server. Use your server’s /sse URL to load it as a remote MCP client and try out your tools directly in the playground.
If you prefer running a local client configuration, you can point a local MCP client to the remote server’s /sse endpoint. The client can then access the tools exposed by your MCP server as if they were running locally.