Self-hosted MCP tunneling

Expose your local MCP servers to the world — without opening a port

MCP Bridge relays public HTTP requests to the Model Context Protocol servers running on your machine, over a secure outbound WebSocket. No router configuration, no static IP, no inbound firewall rules.

Checkout on github See how it works

public request

# any MCP client can call your local server
GET https://bridge.example.com/mcp/alice-notes/tools/list

→ forwarded to your desktop agent, then to localhost

How it works

Four steps between your laptop and a public MCP endpoint.

1
Create an account
Sign up and register the MCPs you want to expose, each with a name and the local port it runs on.
2
Run the desktop agent
The agent opens a single outbound WebSocket connection to the bridge — nothing needs to be reachable from the internet.
3
Get a public URL
Every MCP gets a stable address: bridge.example.com/mcp/<username>-<mcp-name>.
4
Use it anywhere
Point ChatGPT or any other MCP-capable client at the URL. Requests are relayed to your machine and back in real time.

One relay, zero open ports

The backend never connects to your machine — your agent always dials out to it.

MCP client

ChatGPT or any other tool that speaks MCP over HTTP

MCP Bridge

Routes each request to the right account's connected agent

Desktop agent

Forwards the request to your local MCP server and sends the response back

Because the connection is always initiated by your desktop agent, there's nothing to expose, forward, or leave open on your network.

Built for running MCPs from anywhere

A small, focused feature set instead of a general-purpose tunnel.

No port forwarding

Your agent connects outbound only. No router changes, no static IP, no inbound rules.

Multiple MCPs per account

Account-scoped access

Every proxied request resolves to a specific MCP owned by a specific, authenticated account.

Real-time relay

Requests are forwarded over a persistent WebSocket connection with correlation IDs and timeouts.

Works with any MCP client

Plain HTTP in, plain HTTP out — compatible with ChatGPT and any other MCP-speaking client.

Open, self-hostable architecture

A documented WebSocket protocol and a clean backend you can run and extend yourself.

Frequently asked questions

What is an MCP server?

The Model Context Protocol is a standard way for AI tools to call out to external servers for context and actions. MCP Bridge doesn't run MCP servers for you — it exposes ones you already run locally.

Is my machine exposed to the internet?

No. Your desktop agent only makes an outbound connection to the bridge. The bridge never initiates a connection to your machine or localhost.

Can I self-host the backend?

Yes. MCP Bridge is a standard NestJS backend with an open, versioned WebSocket protocol, designed to be run on your own infrastructure.

Can I run more than one MCP at a time?

Yes. A single desktop agent connection can serve every MCP configured on your account, each reachable at its own public URL.

Ready to expose your first MCP?

Create an account, register your local MCP, and get a public URL in minutes.

Checkout on github