- Home
- MCP servers
- Remote
Remote
- typescript
0
GitHub Stars
typescript
Language
6 months ago
First Indexed
3 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
You can deploy a remote MCP server that runs on Cloudflare Workers to expose your tools to MCP clients without requiring authentication. This setup lets you run your own server and connect MCP clients, such as a playground or desktop tool, to access your tools securely over the MCP protocol.
How to use
Connect your MCP client to the remote server URL provided by the deployment. For example, you can point the Cloudflare AI Playground to your deployed server to try out your tools directly from a browser-based client. You can also connect from local MCP clients by using the remote server URL with the standard sse endpoint.
How to install
Prerequisites: ensure you have Node.js and npm installed on your machine. You will also need access to Cloudflare tooling if you plan to deploy directly to Cloudflare Workers.
Install and initialize the remote MCP server project locally using the following command. This creates a new MCP server project configured for a Cloudflare Workers deployment.
npm create cloudflare@latest -- my-mcp-server --template=cloudflare/ai/demos/remote-mcp-authless
If you prefer deploying without local setup, you can deploy your MCP server to Cloudflare Workers by using the web-based deployment flow, which sets up a remote server URL similar to remote-mcp-server-authless.YOURACCOUNT.workers.dev/sse.
Additional notes
Customize your MCP server by adding tools. Open the file that defines the server (for example, the init method of your server entry) and register each tool with the server using the dedicated method to expose it as an MCP tool.
Connect Claude Desktop or other local MCP clients to the remote server by configuring the MCP client to use the remote URL. If you use Claude Desktop, place the remote URL in the client configuration so the tools become available once the client restarts.
Example client configuration for a local setup (to be used by a remote proxy): the server URL is the remote MCP endpoint and can be swapped with your actual deployment URL.
{
"mcpServers": {
"calculator": {
"command": "npx",
"args": [
"mcp-remote",
"http://localhost:8787/sse" // or remote-mcp-server-authless.your-account.workers.dev/sse
]
}
}
}