home / mcp / remote mcp server
Provides a remote MCP server with Cloudflare deployment, enabling OAuth login and tool access via SSE.
Configuration
View docs{
"mcpServers": {
"jakepartusch-remote-mcp-server-2": {
"url": "https://worker-name.account-name.workers.dev/sse"
}
}
}You can run a remote MCP server on Cloudflare Workers, connect it from local development tools, and route Claude Desktop traffic through a local proxy. This guide walks you through developing, testing, deploying, and connecting to the remote MCP server from both local and remote MCP clients.
Explore and control your MCP server from your MCP client and from Claude Desktop. Start locally to develop and test, then deploy to Cloudflare to enable remote access. Use the MCP Inspector to discover available tools, test login, and call endpoints. Connect Claude Desktop to either your local proxy or the deployed remote server to access tools in-context and trigger actions from prompts.
Prerequisites: install Node.js and npm, and ensure you have a working internet connection.
Install and run the server locally for development.
# clone the repository
git clone [email protected]:cloudflare/ai.git
# install dependencies
cd ai
npm install
# run locally
npx nx dev remote-mcp-serverConfiguration and deployment steps are provided to enable both local development and remote deployment. You can connect the MCP Inspector to your local server, and you can configure Claude Desktop to talk to either the local proxy or the deployed remote server.
To connect Claude Desktop to the local MCP server, replace the configuration with the local proxy endpoint that the server exposes at /sse.
To deploy to Cloudflare, create the OAuth KV namespace, update the deployment configuration, and run the deployment command.
To connect a remote MCP client, use the inspector and point it to the workers.dev URL for the deployed worker.
Debugging tips include restarting Claude, testing direct MCP server access via the command-line, and clearing authentication state if you encounter issues.
A tool to explore the MCP API using the inspector UI. You start it with a single command and connect to your MCP server via SSE transport.
A proxy tool that connects to a remote MCP server over HTTP(S) using a standard command line invocation.