Remote MCP Server on Cloudflare

@mehmet-arikan

Repository

Basic information

About Remote MCP Server on Cloudflare

No overview available yet

#remote-mcp-server #cloudflare #mcp-inspector

Remote MCP Server on Cloudflare config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "remote-mcp-server-mehmet-arikan": {
      "command": "npx",
      "args": [
        "nx",
        "dev",
        "remote-mcp-server"
      ]
    }
  }
}

Remote MCP Server on Cloudflare tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is Remote MCP Server on Cloudflare?

Remote MCP Server on Cloudflare is a project to deploy a remote MCP (Model Context Protocol) server on Cloudflare Workers, complete with OAuth login. It provides a ready‑to‑use setup for developers who want to run MCP servers in the cloud and connect them to clients such as Claude Desktop or the MCP Inspector.

How to use Remote MCP Server on Cloudflare?

Clone the repository, install dependencies, and run locally with npx nx dev remote-mcp-server. For production, create a Cloudflare KV namespace (npx wrangler kv namespace create OAUTH_KV), add its ID to wrangler.jsonc, and deploy with npm run deploy. Connect via the MCP Inspector using SSE transport, or via Claude Desktop by adding an entry to the config file that invokes npx mcp-remote pointing to your server’s /sse endpoint.

Key features of Remote MCP Server on Cloudflare

OAuth‑protected MCP server on Cloudflare Workers
Local development with live reload
Deploy to Cloudflare’s edge network
SSE transport for MCP clients
MCP Inspector integration for testing
Claude Desktop integration via a local proxy

Use cases of Remote MCP Server on Cloudflare

Run a remote MCP server accessible from anywhere
Securely expose MCP tools behind OAuth login
Integrate with Claude Desktop for AI‑powered tool calling
Prototype and debug MCP servers using the official Inspector

Frequently asked questions

What authentication does the server use?

The server uses OAuth with a mock login screen during local development. In the MCP Inspector you enter any email and password to authenticate.

What is the OAUTH_KV namespace for?

It is a Cloudflare KV namespace that stores OAuth session data. You must create it with `wrangler kv namespace create OAUTH_KV` and add the resulting ID to `wrangler.jsonc` before deploying.

How do I connect Claude Desktop to the remote server?

Update your Claude Desktop configuration file (found under Settings > Developer > Edit Config) to include an entry that runs `npx mcp-remote` with your server’s `workers.dev` URL appended with `/sse`.

What transport does the server use?

It uses Server‑Sent Events (SSE) as the transport protocol. The MCP Inspector and Claude proxy connect to the `/sse` endpoint.

How can I debug connection issues?

Use `npx mcp-remote http://localhost:8787/sse` on the command line to test directly. Restart Claude, or clear the files in `~/.mcp-auth` if needed.

Comments

More Cloud & Infrastructure MCP servers

SimpleBackups

SimpleBackups is automated backup management for databases, servers, cloud storage and SaaS apps. It covers Supabase, Neon, PlanetScale, PostgreSQL, MySQL, MongoDB, and apps like Notion, GitHub and Linear. This connector

Terraform MCP Server

hashicorp

The Terraform MCP Server provides seamless integration with Terraform ecosystem, enabling advanced automation and interaction capabilities for Infrastructure as Code (IaC) development.

1.5K

Backblaze B2 MCP server

backblaze-labs

MCP server for Backblaze B2 Cloud Storage: a focused, safe 40-tool surface (17 native B2 SDK, 19 S3 data-plane, 4 analytics) for any MCP-compatible AI client, currently incubating in Backblaze-Labs

AWS MCP Servers

awslabs

Open source MCP Servers for AWS

9.4K

Tessryx

Build and run websites, APIs, automations, and admin tools from chat. Your agent creates the data, logic, pages, and scheduled jobs; Tessryx hosts them on your own domain. No code generated, nothing to deploy.