what is Remote MCP Server on Cloudflare?
Remote MCP Server on Cloudflare is a server setup that allows users to run a Model Context Protocol (MCP) server on Cloudflare Workers, enabling remote access and interaction with various tools through a web interface.
how to use Remote MCP Server on Cloudflare?
To use the Remote MCP Server, clone the repository, install dependencies, and run the server locally. You can then connect to the server using the MCP Inspector or integrate it with Claude Desktop for enhanced functionality.
key features of Remote MCP Server on Cloudflare?
- Easy setup on Cloudflare Workers with OAuth login.
- Local development and testing capabilities.
- Integration with MCP Inspector for exploring APIs.
- Ability to connect with Claude Desktop for advanced tool usage.
use cases of Remote MCP Server on Cloudflare?
- Running a remote MCP server for collaborative projects.
- Integrating with AI tools like Claude for enhanced productivity.
- Testing and debugging MCP APIs in a local environment.
FAQ from Remote MCP Server on Cloudflare?
- Can I run this server without Cloudflare?
No, this server is specifically designed to run on Cloudflare Workers.
- Is there a cost associated with using Cloudflare Workers?
Cloudflare Workers has a free tier, but usage beyond that may incur costs.
- How do I debug connection issues?
Restarting the server or clearing authentication files can help resolve connection issues.
Remote MCP Server on Cloudflare
Let's get a remote MCP server up-and-running on Cloudflare Workers complete with OAuth login!
Develop locally
# clone the repository
git clone git@github.com:cloudflare/ai.git
# install dependencies
cd ai
npm install
# run locally
npx nx dev remote-mcp-server
You should be able to open http://localhost:8787/
in your browser
Connect the MCP inspector to your server
To explore your new MCP api, you can use the MCP Inspector.
- Start it with
npx @modelcontextprotocol/inspector
- Within the inspector, switch the Transport Type to
SSE
and enterhttp://localhost:8787/sse
as the URL of the MCP server to connect to, and click "Connect" - You will navigate to a (mock) user/password login screen. Input any email and pass to login.
- You should be redirected back to the MCP Inspector and you can now list and call any defined tools!


Connect Claude Desktop to your local MCP server
The MCP inspector is great, but we really want to connect this to Claude! Follow Anthropic's Quickstart and within Claude Desktop go to Settings > Developer > Edit Config to find your configuration file.
Open the file in your text editor and replace it with this configuration:
{
"mcpServers": {
"math": {
"command": "npx",
"args": [
"mcp-remote",
"http://localhost:8787/sse"
]
}
}
}
This will run a local proxy and let Claude talk to your MCP server over HTTP
When you open Claude a browser window should open and allow you to login. You should see the tools available in the bottom right. Given the right prompt Claude should ask to call the tool.


Deploy to Cloudflare
npx wrangler kv namespace create OAUTH_KV
- Follow the guidance to add the kv namespace ID to
wrangler.jsonc
npm run deploy
Call your newly deployed remote MCP server from a remote MCP client
Just like you did above in "Develop locally", run the MCP inspector:
npx @modelcontextprotocol/inspector@latest
Then enter the workers.dev
URL (ex: worker-name.account-name.workers.dev/sse
) of your Worker in the inspector as the URL of the MCP server to connect to, and click "Connect".
You've now connected to your MCP server from a remote MCP client.
Connect Claude Desktop to your remote MCP server
Update the Claude configuration file to point to your workers.dev
URL (ex: worker-name.account-name.workers.dev/sse
) and restart Claude
{
"mcpServers": {
"math": {
"command": "npx",
"args": [
"mcp-remote",
"https://worker-name.account-name.workers.dev/sse"
]
}
}
}
Debugging
Should anything go wrong it can be helpful to restart Claude, or to try connecting directly to your MCP server on the command line with the following command.
npx mcp-remote http://localhost:8787/sse
In some rare cases it may help to clear the files added to ~/.mcp-auth
rm -rf ~/.mcp-auth