Overview
What is Remote MCP Server on Cloudflare?
A Model Context Protocol (MCP) server deployed on Cloudflare Workers, using SSE transport and Durable Objects. It provides a remote MCP endpoint accessible via URL.
How to use Remote MCP Server on Cloudflare?
Configure your MCP client with the url set to the server’s SSE endpoint (e.g., http://localhost:8787/sse in the provided mcp.json example). Deploy the server to Cloudflare by running npm run deploy (uses wrangler). The deployment requires a Cloudflare Workers paid plan if Durable Objects are used.
Key features of Remote MCP Server on Cloudflare
- SSE-based MCP transport
- Durable Objects for state management
- Deployed via wrangler (
npm run deploy) - Works with local development URL
localhost:8787/sse - Uses Cloudflare Workers and Assets binding
Use cases of Remote MCP Server on Cloudflare
—
FAQ from Remote MCP Server on Cloudflare
What transport protocol does it use?
It uses SSE (Server-Sent Events) as shown by the /sse path in the example URL.
What runtime or dependencies are required?
The server is built with Node.js (v20.17.0 seen in the deploy log) and uses wrangler for Cloudflare deployment.
Does it require a paid Cloudflare plan?
Yes, the Durable Object binding (MCP_OBJECT) triggers an error unless the account is on a paid Workers plan.
Where is the server code hosted?
The README references a note page at https://note.linkof.link/13a9p7.html for additional details, but the deployment scripts and config are provided directly.
How do I test the server locally?
The mcp.json snippet points to http://localhost:8787/sse, suggesting a local development server runs on port 8787.