Remote MCP Server
by irvinebroque
This project provides a remote MCP (Model Context Protocol) server that can be deployed on Cloudflare Workers. It allows you to connect to the server using tools like the MCP Inspector and Claude Desktop.
Last updated: N/A
What is Remote MCP Server?
A remote MCP server built to run on Cloudflare Workers, enabling interaction with tools and services using the Model Context Protocol.
How to use Remote MCP Server?
First, develop locally by cloning the repository, installing dependencies, and running the server. Then, connect the MCP inspector or Claude Desktop to the local server. Finally, deploy to Cloudflare by creating a KV namespace and running the deploy script. You can then connect to the deployed server using the MCP inspector or Claude Desktop by updating the configuration with the workers.dev URL.
Key features of Remote MCP Server
Remote MCP server
Cloudflare Workers deployment
OAuth login
MCP Inspector compatibility
Claude Desktop integration
Use cases of Remote MCP Server
Connecting Claude to custom tools
Providing a remote interface for AI models
Experimenting with the Model Context Protocol
Building scalable AI applications
Integrating AI tools with existing workflows
FAQ from Remote MCP Server
How do I connect the MCP Inspector?
How do I connect the MCP Inspector?
Start the inspector, switch the Transport Type to SSE, and enter the server URL (e.g., http://localhost:8787/sse or your workers.dev URL).
How do I connect Claude Desktop?
How do I connect Claude Desktop?
Edit the Claude configuration file to point to your server's URL (either local or workers.dev).
What if something goes wrong?
What if something goes wrong?
Try restarting Claude, or connect directly to your MCP server on the command line using npx mcp-remote.
Where is the Claude config located?
Where is the Claude config located?
Within Claude Desktop go to Settings > Developer > Edit Config to find your configuration file.
What do I do if I have auth issues?
What do I do if I have auth issues?
In some rare cases it may help to clear the files added to ~/.mcp-auth using rm -rf ~/.mcp-auth