How do I use MCP Router?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP Router search the web for latest AI news" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

MCP Router

by marklubin

Overview Schema Related Servers Score Discussions

Python

MCP Router

Extensible MCP server that aggregates multiple backends behind a single endpoint.

Architecture

Claude → CF Worker (OAuth) → Workers VPC → CF Tunnel → MCP Router → [Backends]
                                   │                        ↓
                            (private backbone)         email backend → ProtonMail Bridge
                                                       (add more backends here)

Security: No public DNS exposure. Traffic flows through Cloudflare's private network via Workers VPC binding to a Cloudflare Tunnel with no public hostname.

Related MCP server: todoist-v1-mcp-server

Quick Start

1. Clone and install

curl -LsSf https://astral.sh/uv/install.sh | sh
git clone https://github.com/marklubin/mcp-email-server.git mcp-infrastructure
cd mcp-infrastructure

2. Configure

cp .env.example .env
# Edit .env with your credentials

3. ProtonMail Bridge (one-time)

protonmail-bridge --cli
# > login
# > info  (note the bridge password)

4. Run

uv run python router/server.py

Or with systemd:

./setup.sh
sudo systemctl enable --now mcp-router@$USER

5. Set up Cloudflare Tunnel (for private backend)

cloudflared tunnel login
cloudflared tunnel create mcp-router
# Configure ~/.cloudflared/config.yml (see cloudflare/tunnel-config.yml.example)
sudo systemctl enable --now cloudflared

6. Create Workers VPC Service

In Cloudflare Dashboard → Workers & Pages → Workers VPC:

Create service: mcp-router-vpc
Select tunnel: mcp-router
Target: http://127.0.0.1:8080

7. Deploy Worker

cd cloudflare/worker && npx wrangler deploy

Deployment

The canonical deployed instance runs on oxnard as the systemd unit mcp-router@mark.service.

Steady-state flow:

Edit code locally on a dev machine (clone of this repo).
Commit and push to origin/master.
From the local clone, run ./scripts/deploy.sh — pushes (if needed), SSHes to the remote, runs git pull, and restarts the service.
If dependencies changed (pyproject.toml / uv.lock), deploy.sh's uv sync keeps the venv in sync. If it doesn't, restart will still pick up the new deps on next uv run.

Do not edit code directly on oxnard. The repo is the source of truth — changes made only on the box will drift and get lost. If you must hotpatch in an emergency, copy the fix back into the repo and commit it before doing anything else.

Override the deploy target with MCP_REMOTE=hostname ./scripts/deploy.sh.

Backends

Each backend lives in router/backends/ and exposes tools under its mount prefix.

Backend	Prefix	Purpose
`email`	`email_`	ProtonMail Bridge — list/search/get/send
`browser`	`browser_`	Playwright-over-CDP browser automation
`todoist`	`todoist_`	Todoist tasks/projects
`notifications`	`notify_`	Push notifications + inbox
`discord`	`discord_`	Discord (via user token)
`memory`	`memory_`	Agent memory store
`twitter`	`twitter_`	Twitter read via twitterapi.io
`web`	`web_`	Web search + contents via Exa

Also available but not currently mounted in server.py:

unified_memory.py — proxies all synix MCP tools from the agent-mesh server on salinas. Wire it up by importing + mounting if you want to replace or augment memory.

Email Backend (prefix: `email_`)

Tool	Description
`email_list_emails(mailbox, limit)`	List recent emails
`email_search_emails(query, mailbox, limit, search_body)`	Search by subject, sender, or body
`email_get_email(message_id, mailbox)`	Get full email content
`email_send_email(to, subject, body)`	Send email

Web Backend (prefix: `web_`)

Uses Exa under the hood. Free tier: 1,000 searches/month.

Tool	Description
`web_search(query, num_results, search_type, include_text, include_domains, exclude_domains)`	Web search; optional inline text excerpts
`web_get_contents(urls, max_chars)`	Fetch clean text for one or more URLs

For detailed signatures of other backends, read the source — each tool's docstring is its contract.

Router

Tool	Description
`health()`	Health check with backend status
`logs(lines, service)`	Tail service logs (`mcp-router` or `cloudflared`)

Adding New Backends

Create router/backends/yourbackend.py:

from fastmcp import FastMCP

mcp = FastMCP('yourbackend')

@mcp.tool()
async def your_tool(arg: str) -> dict:
    """Your tool description."""
    return {'result': 'value'}

Mount in router/server.py:

from backends import yourbackend
router.mount(yourbackend.mcp, prefix='yourbackend')

Also append the prefix to the health() backend list.

If the backend needs secrets, add them to .env.example and .env.
Commit and run ./scripts/deploy.sh. Tools appear as yourbackend_your_tool.

Claude Config

{
  "mcpServers": {
    "router": {
      "url": "https://mcp-router-proxy.melubin.workers.dev/mcp",
      "transport": "sse"
    }
  }
}

Environment Variables

See .env.example for the full list. Required for core operation:

MCP_SECRET=              # API key for auth from CF Worker
ROUTER_HOST=127.0.0.1
ROUTER_PORT=8080
PROTON_BRIDGE_HOST=127.0.0.1
PROTON_BRIDGE_IMAP_PORT=1143
PROTON_BRIDGE_SMTP_PORT=1025
PROTON_BRIDGE_USER=you@proton.me
PROTON_BRIDGE_PASSWORD=bridge-password

Backend-specific keys (only required if the backend is mounted):

EXA_API_KEY=             # web search
TODOIST_API_TOKEN=       # todoist
TWITTERAPI_IO_KEY=       # twitter
DISCORD_TOKEN=           # discord
MESH_SERVER_URL=         # memory
MESH_TOKEN=              # memory
AGENT_MESH_MCP_URL=      # unified_memory (if mounted)

Project Structure

mcp-infrastructure/
├── router/
│   ├── server.py                   # Main router, mounts backends
│   └── backends/
│       ├── __init__.py
│       ├── email.py                # ProtonMail
│       ├── browser.py              # Playwright over CDP
│       ├── todoist.py              # Todoist
│       ├── notifications.py        # Push/inbox
│       ├── discord.py              # Discord user-token
│       ├── memory.py               # Agent memory
│       ├── twitter.py              # Twitter (twitterapi.io)
│       ├── web.py                  # Web search (Exa)
│       └── unified_memory.py       # Synix proxy (not mounted by default)
├── services/
│   ├── mcp-router.service          # systemd template for router
│   ├── cloudflared.service         # systemd service for tunnel
│   ├── headless-brave.service      # headless browser
│   └── protonmail-bridge.service   # ProtonMail Bridge
├── cloudflare/
│   ├── tunnel-config.yml.example   # Tunnel config template
│   └── worker/                     # CF Worker for OAuth + VPC proxy
├── scripts/
│   ├── deploy.sh                   # Push and deploy to remote
│   ├── logs.sh                     # View service logs
│   ├── status.sh                   # Check service status
│   ├── tunnel.sh                   # Manage Cloudflare Tunnel
│   ├── test-email.sh               # Test email tools
│   ├── test.sh                     # Run tests
│   ├── browser-connect.sh          # Connect to CDP browser
│   ├── run-headless-brave.sh       # Launch headless Brave
│   ├── run-headless-firefox.sh     # Launch headless Firefox + VNC
│   └── notify-check.sh             # Notification health check
├── setup.sh                        # One-shot setup script
├── pyproject.toml                  # Python dependencies
└── .env.example                    # Config template

Management Scripts

Script	Purpose
`scripts/deploy.sh`	Push and deploy to remote (respects `MCP_REMOTE` env var)
`scripts/logs.sh [n]`	View last n log lines
`scripts/status.sh`	Check service status
`scripts/tunnel.sh [status\|logs\|restart]`	Manage tunnel
`scripts/test-email.sh`	Test email tools
`scripts/test.sh`	Run tests
`scripts/browser-connect.sh`	Connect to the CDP-exposed browser
`scripts/run-headless-brave.sh`	Launch headless Brave with CDP
`scripts/run-headless-firefox.sh`	Launch headless Firefox + VNC on :99
`scripts/notify-check.sh`	Notification backend health check

This server cannot be installed

license - not found

quality - not tested

maintenance

How are these scores calculated?

Maintenance

–Maintainers

–Response time

–Release cycle

–Releases (12mo)

Commit activity

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

Remote MCP Server on
Developer Tools Cloud Platforms
sourabharsh
F
license
-
quality
C
maintenance
A Model Context Protocol server implementation designed to run on Cloudflare Workers with integrated OAuth authentication. It enables hosting and securely accessing MCP tools remotely via SSE transport from clients like Claude Desktop.
Last updated 2025-06-27
todoist-v1-mcp-server
App Automation Workplace & Productivity Project Management
christulino
A
license
A
quality
C
maintenance
A clean, reliable MCP (Model Context Protocol) server for Todoist — built on the Todoist unified API v1.
Last updated 2026-05-07
20
1
MIT
Todoist MCP Server
Project Management Workplace & Productivity
deepakjois
A
license
-
quality
D
maintenance
A proof-of-concept MCP server that interacts with Todoist using OAuth-based authorization and is deployed on Cloudflare Workers.
Last updated 2025-06-18
4
MIT
todoist-mcp
Project Management Workplace & Productivity
lawheitung
A
license
-
quality
C
maintenance
A Cloudflare Worker-based MCP server that enables AI assistants to read and manage Todoist tasks through tools like get_tasks, add_task, update_task, complete_task, delete_task, and move_task.
Last updated 2026-06-22
327
MIT

View all related MCP servers

Related MCP Connectors

microservices.sh
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
XMemo
User-owned memory for AI agents, Copilot, Claude, IDEs, CLIs, and chat apps over remote MCP.
hithereiamaliff-mcp-nextcloud
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…

View all MCP Connectors

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/marklubin/mcp-email-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

MCP Router

Architecture

Quick Start

1. Clone and install

2. Configure

3. ProtonMail Bridge (one-time)

4. Run

5. Set up Cloudflare Tunnel (for private backend)

6. Create Workers VPC Service

7. Deploy Worker

Deployment

Backends

Email Backend (prefix: email_)

Web Backend (prefix: web_)

Router

Adding New Backends

Claude Config

Environment Variables

Project Structure

Management Scripts

Maintenance

Resources

Looking for Admin?

Related MCP Servers

Remote MCP Server on

todoist-v1-mcp-server

Todoist MCP Server

todoist-mcp

Related MCP Connectors

Latest Blog Posts

MCP directory API

Email Backend (prefix: `email_`)

Web Backend (prefix: `web_`)