Expose your local MCP servers to the world — without opening a port
# 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 localhostHow 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 Loop
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.
No desktop app? Use the browser extension
Install the MCP Loop Chrome extension and the dashboard tunnels your MCPs straight from the browser — no Electron install required.
Automatic handoff
Log into the dashboard as a normal website and the extension picks up your session automatically — no separate login in the extension itself.
Same protocol
Its background service worker speaks the exact same tunnel protocol as the desktop agent, forwarding to your local MCP servers the same way.
Always in sync
Add, remove, or edit MCPs in the dashboard and the extension's local routing table updates live, no reconnect needed.
Publish and install MCPs from a marketplace
Browse MCPs other users have published, or share your own — versioned, searchable, and installed with one click.
Browse, search, and sort
Find listings by name, sorted by release date or download count, with a version history for each one.
One-click install
The desktop agent downloads the chosen version, unzips it, and cleans up the zip automatically — with a live progress bar the whole way through.
Stay up to date
Installed items are flagged the moment a newer version is published, with an Update button right there in the marketplace.
Manage everything from three tabs
Publishing and running MCPs comes with its own dashboard tabs, right next to the ones that manage the tunnel itself.
My Releases
Edit name, description, and visibility; add or remove preview images; upload new versions or delete old ones — all from one place per listing.
On this system
See every MCP you've installed locally, which version, and where it landed on disk — with an Update button the moment a newer version ships.
Settings
Pick where the desktop agent unpacks downloaded MCPs — the one setting that controls where installed listings live on disk.
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
Register as many local MCP servers as you like, each with its own name and public URL.
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 Loop 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 Loop 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.
Do I need to install the desktop app?
No — install the MCP Loop Chrome extension instead and open the dashboard as a normal website. It tunnels the same way, without Electron.
Ready to expose your first MCP?
Create an account, register your local MCP, and get a public URL in minutes.
Checkout on github