Skip to main content
Glama
Remote MCP Server on Cloudflare

Remote MCP Server on Cloudflare

Remote MCP Server on Cloudflare

Let's get a remote MCP server up-and-running on Cloudflare Workers complete with OAuth login!

Develop locally

# clone the repository
git clone https://github.com/cloudflare/ai.git
# Or if using ssh:
# git clone git@github.com:cloudflare/ai.git

# install dependencies
cd ai
# Note: using pnpm instead of just "npm"
pnpm install

# run locally
npx nx dev remote-mcp-server

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

Related MCP server: Remote MCP Server on Cloudflare

Connect the MCP inspector to your server

To explore your new MCP api, you can use the MCP Inspector.

  • Start it with npx @modelcontextprotocol/inspector

  • Within the inspector, switch the Transport Type to SSE and enter http://localhost:8787/sse as the URL of the MCP server to connect to, and click "Connect"

  • You will navigate to a (mock) user/password login screen. Input any email and pass to login.

  • You should be redirected back to the MCP Inspector and you can now list and call any defined tools!

Connect Claude Desktop to your local MCP server

The MCP inspector is great, but we really want to connect this to Claude! Follow Anthropic's Quickstart and within Claude Desktop go to Settings > Developer > Edit Config to find your configuration file.

Open the file in your text editor and replace it with this configuration:

{
  "mcpServers": {
    "math": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://localhost:8787/sse"
      ]
    }
  }
}

This will run a local proxy and let Claude talk to your MCP server over HTTP

When you open Claude a browser window should open and allow you to login. You should see the tools available in the bottom right. Given the right prompt Claude should ask to call the tool.

Deploy to Cloudflare

  1. npx wrangler kv namespace create OAUTH_KV

  2. Follow the guidance to add the kv namespace ID to wrangler.jsonc

  3. npm run deploy

Call your newly deployed remote MCP server from a remote MCP client

Just like you did above in "Develop locally", run the MCP inspector:

npx @modelcontextprotocol/inspector@latest

Then enter the workers.dev URL (ex: worker-name.account-name.workers.dev/sse) of your Worker in the inspector as the URL of the MCP server to connect to, and click "Connect".

You've now connected to your MCP server from a remote MCP client.

Connect Claude Desktop to your remote MCP server

Update the Claude configuration file to point to your workers.dev URL (ex: worker-name.account-name.workers.dev/sse) and restart Claude

{
  "mcpServers": {
    "math": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://worker-name.account-name.workers.dev/sse"
      ]
    }
  }
}

Debugging

Should anything go wrong it can be helpful to restart Claude, or to try connecting directly to your MCP server on the command line with the following command.

npx mcp-remote http://localhost:8787/sse

In some rare cases it may help to clear the files added to ~/.mcp-auth

rm -rf ~/.mcp-auth

Available Tools

2 tools
get_current_dateB

获取当前日期, 如果用户没有提供日期, 则返回当前日期, 如果用户提供的是相对单位, 如前天, 昨天, 明天, 则返回相对单位后的日期

Inputs: date (required).

get_current_weatherC

Get weather info for a given city.

Inputs: city (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: one handles date calculations and the other provides weather information. There is no overlap in functionality, making it impossible for an agent to confuse them.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun naming pattern (get_current_date and get_current_weather). The structure is uniform and predictable, with no deviations in style or convention.

    Tool Count2/5

    With only two tools, the server feels thin and under-scoped for a 'Remote MCP Server on Cloudflare', which implies broader capabilities. The tools are unrelated (date and weather), suggesting a lack of cohesive domain coverage.

    Completeness2/5

    The server's purpose is unclear from the toolset, but the two tools cover unrelated domains (date and weather) without any supporting operations. There are significant gaps, as neither domain has a complete lifecycle (e.g., no date formatting or historical weather), and the overall surface is severely incomplete for any coherent workflow.

    Related MCP Connectors

    Related MCP Servers