home / mcp / remote mcp server authless3

Remote MCP Server Authless3

Provides a remote HTTP MCP server and local stdio proxy access to define and use MCP tools.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "asdasgusdas-remote-mcp-server-authless3": {
      "url": "https://remote-mcp-server-authless.<your-account>.workers.dev/sse"
    }
  }
}

You can run a remote MCP server that serves tools over HTTP or via a local stdio client, enabling you to access and use your tools from any MCP-compatible client or editor. This approach is useful for quick experimentation, demos, or integrating with clients like Claude Desktop or Cloudflare AI Playground without embedding authentication.

How to use

Connect to your remote MCP server from any MCP client to access the tools you’ve defined. You can use the Cloudflare-backed server over HTTP, or run a local proxy that exposes your server to your local environment. In practice, you will either point a client at the remote server’s HTTP URL or run a local proxy via npx and connect through the proxy to the same HTTP endpoint.

How to install

Prerequisites you need before starting:

- Node.js installed on your machine.

- An MCP client or environment that can consume standard MCP server configurations.

Step-by-step setup to enable both remote HTTP access and a local stdio proxy extends from the same codebase. Follow these steps to prepare, run, and connect.

# Step 1: Install the MCP server scaffold (example command shown for setup)
# Use the exact command from your environment when you deploy
npm create cloudflare@latest -- my-mcp-server --template=cloudflare/ai/demos/remote-mcp-authless

# Step 2: Customize your MCP server
# In your source, add tools inside the init() method using this.server.tool(...)

# Step 3: Run a local proxy (optional for local testing)
npx mcp-remote http://localhost:8787/sse

# Step 4: Connect to the remote Cloudflare-hosted server (if you deployed it)
# The server will be available at a URL similar to
# https://remote-mcp-server-authless.your-account.workers.dev/sse

# Step 5: Connect a client to the appropriate endpoint
# For a local proxy: http://localhost:8787/sse
# For the remote server: remote-mcp-server-authless.your-account.workers.dev/sse

Additional sections

Configuration overview
- Remote HTTP MCP server URL: https://remote-mcp-server-authless.<your-account>.workers.dev/sse
- Local stdio proxy (via npx) to access the same server: npx mcp-remote http://localhost:8787/sse
- Optional remote URL through the local proxy: npx mcp-remote remote-mcp-server-authless.your-account.workers.dev/sse

Notes on customization - To add your tools, define each tool inside the init() method of your MCP server’s source with this.server.tool(...). This is how you extend the server’s capabilities with new commands or endpoints.

Security and access - When using a public remote server, consider attaching authentication if your workflow requires restricting access to your MCP tools. For local development, a local proxy can help you test privately before exposing a remote URL.