Building a Remote MCP Server on Cloudflare (Without Auth)

by jingwei950

136 downloads
Not rated
GitHub

About

# Building a Remote MCP Server on Cloudflare (Without Auth) This example allows you to deploy a remote MCP server that doesn't require authentication on Cloudflare Workers. ## Get started: [![Deploy to…

Details

Author
jingwei950
Downloads
136
Categories
Developer Tools

- One‑click deployment to Cloudflare Workers.
- No authentication required on the server.
- Custom MCP tools defined in TypeScript.
- Secure secret management with Cloudflare encrypted variables.
- Local development secrets via .dev.vars.
- Connectable to Cloudflare AI Playground or Claude Desktop via mcp-remote proxy.

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

  1. Download and install Highlight from highlightai.com/download
  2. Navigate to the plugins tab and select "Add Custom Plugin"
  3. Configure the plugin with the settings below
    Plugin Name Building a Remote MCP Server on Cloudflare (Without Auth)
    Command (node, npx, python, etc.)

    Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.

  4. Enable "Start Automatically" if you want the plugin to start when Highlight launches

From the repository

Deploy the server using the one‑click “Deploy to Workers” button or by cloning the repository and running npx wrangler deploy. Customize MCP tools inside src/index.ts using this.server.tool(...). Manage production secrets with Cloudflare’s encrypted variables via wrangler secret put or the dashboard; use a local .dev.vars file for development.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "building a remote mcp server on cloudflare (without auth)": {
            "enterprise-clickup-mcp-server": {
                "command": "npx",
                "args": [
                    "wrangler",
                    "login"
                ]
            }
        }
    }
}

McpServers

{
    "enterprise-clickup-mcp-server": {
        "command": "npx",
        "args": [
            "wrangler",
            "login"
        ]
    }
}

Building a Remote MCP Server on Cloudflare (Without Auth)

This example allows you to deploy a remote MCP server that doesn't require authentication on Cloudflare Workers.

Get started:

Deploy to Workers

This will deploy your MCP server to a URL like: remote-mcp-server-authless.<your-account>.workers.dev/sse

Alternatively, you can use the command line below to get the remote MCP Server created on your local machine:

npm create cloudflare@latest -- my-mcp-server --template=cloudflare/ai/demos/remote-mcp-authless

Deploying to Your Own Cloudflare Worker

Instead of using the one-click deploy button, you can clone this repository and deploy it manually to your Cloudflare account.

1. Clone the repository:

    git clone <repository-url>
cd <repository-directory>

2. Install dependencies:
    npm install

3. Login to Cloudflare:
    npx wrangler login

4. Deploy:
    npx wrangler deploy

This command will build and deploy your worker. Wrangler will provide you with the URL where your worker is deployed (e.g., my-mcp-server.<your-account>.workers.dev/sse).

Managing Secrets (API Keys)

If your custom tools require API keys or other secrets, you need to configure them securely.

Production Secrets (Cloudflare Dashboard/Wrangler)

For your deployed worker, use Cloudflare's secret management:

1. Using Wrangler:

    npx wrangler secret put YOUR_SECRET_NAME
    

Wrangler will prompt you to enter the secret value. This value will be encrypted and securely stored, accessible only to your worker code.

2. Using Cloudflare Dashboard:
Go to your Worker in the Cloudflare dashboard -> Settings -> Variables -> Environment Variables -> Add Variable. Make sure to click "Encrypt" to store it securely.

Local Development Secrets (.dev.vars)

For local testing using npx wrangler dev, create a file named .dev.vars in the root of your project directory. Do not commit this file to Git. Add your secrets to this file like so:

```plaintext

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.