Remote

You can deploy a remote MCP server that exposes your tools to MCP clients without requiring authentication. This setup lets you connect from cloud playgrounds or local MCP clients to run your tools remotely, enabling streamlined testing and collaboration across environments.

How to use

Connect to your remote MCP server from an MCP client to access your tools in a browser or desktop app. Use the cloud-hosted URL to reach the server's SSE endpoint, or run a local proxy configuration that points an MCP client at your server. When you connect, your tools will appear in the client and you can invoke them as you would with a locally hosted MCP server. You can also integrate with the Cloudflare AI Playground for quick testing, or configure a local client like Claude Desktop to call the remote server through the mcp-remote proxy.

How to install

Prerequisites: ensure Node.js and npm are installed on your machine, or have Python available if you prefer Python tooling. You will also need access to a terminal or command prompt.

Step 1: Deploy the remote MCP server to Cloudflare Workers or a similar host using the provided deployment flow. Step 2: Verify you have the remote server URL available, which will resemble the pattern shown in the deployment instructions.

Step 3: Add local or remote MCP client configurations to connect to your server as shown in the configuration examples.

Additional content

Custom tools are added inside the server’s initialization logic. You define each tool with a dedicated API or command that the MCP client will call. For example, you can extend your server with new tools by invoking a tool-registration method in the server’s startup routine.

Your remote MCP server can be connected from external clients using a standard HTTP-based endpoint or via a local stdio proxy. The HTTP path for remote access ends with /sse and is hosted at a domain like remote-mcp-server-authless.<your-account>.workers.dev/sse. If you prefer local development, you can point a client at http://localhost:8787/sse through the mcp-remote proxy.

Example client configuration for Claude Desktop shows how to direct the tool runner to the remote server or a localhost proxy. The configuration uses the mcp-remote wrapper to route tool calls to the appropriate SSE endpoint.

Notes on security and usage

This setup demonstrates an authless remote MCP server. Treat it as a development or testing environment. If you move to production, consider enabling authentication or access controls to protect your tools and data.