Remote

Provides a remote MCP server on Cloudflare with OAuth login and local testing capabilities.

typescript

0

GitHub Stars

typescript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "sriram-mk1-remote-mcp-server-bearer-auth": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://localhost:8787/sse",
        "--header",
        "Authorization: Bearer ${AUTH_TOKEN}"
      ],
      "env": {
        "AUTH_TOKEN": "..."
      }
    }
  }
}

You run a remote MCP server on Cloudflare Workers and connect to it from MCP clients using a bearer-authenticated stream. This setup lets you explore, test, and deploy an MCP server that provides a secure, OAuth-enabled interface for your tooling pipelines.

How to use

You interact with the MCP server from an MCP client, typically by connecting to the server’s SSE endpoint and providing a bearer token for authorization. Use the MCP Inspector to explore available tools and verify that your token is accepted. Once connected, you can list available tools and run them to observe responses and headers you control from the client.

How to install

Prerequisites you need before starting are Node.js and npm. Ensure you have a working Node environment to install dependencies and run local development servers.

Step-by-step setup locally to run the MCP server and connect your inspector:

# 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-bearer-auth

You should be able to open http://localhost:8787/ in your browser.

## Additional sections

Configuration and usage notes: you run the local server and connect to it through the MCP Inspector to verify OAuth-enabled access. The local server exposes an SSE endpoint at /sse that the inspector and clients can connect to, using a bearer token for authorization.

If you want to connect Claude Desktop or another MCP client, you can point the client at the local SSE URL http://localhost:8787/sse and provide the Authorization header with your token. The client can then list tools and execute supported actions.

Deploying to Cloudflare will prepare a remote instance that you can call from anywhere. Use the deployment command provided in your workflow to publish the Worker and expose the same /sse endpoint for remote clients.

Debugging tips: if the server isn’t responding, restart Claude or run the remote MCP command to test connectivity from the local environment. You can also clear local authentication data if you encounter persistent auth issues.

## Troubleshooting and debugging

If you experience issues connecting to the local server or the deployed remote server, restart the local process and retry the connection through the MCP Inspector. You can also test the remote endpoint directly with a command-line helper to verify SSE availability and token handling.

## Tools and endpoints

The MCP Inspector is used to connect to the server and explore tools. You can list tools and run them to inspect Authorization headers and responses. Two core tooling actions described are starting the inspector and executing the getToken operation to validate your token handling.

## Available tools

### inspector

Start the MCP Inspector to connect to the MCP server, switch to SSE transport, provide the server URL, and authenticate with a bearer token.

### getToken

Run the getToken tool in the inspector to verify that the Authorization header you configured is being returned correctly.