Connect Claude in your browser

Claude drives Creator through two of its three clients, and the browser is the one that does not.

Where you use Claude	Works with this alpha?	Page
Claude Desktop, the app on your PC	Yes	Connect Claude Desktop
Claude Code, in a terminal	Yes	Connect Claude Code
claude.ai, in a browser	No, it needs a relay this alpha does not ship	this page

If you have Claude, you already have a way in. Pick whichever of the first two you use and follow its page. Nothing on this page is needed for either of them.

Why the browser cannot

While Creator is open it can run a small server of its own, and it listens on 127.0.0.1: your own machine and nothing else. No port is opened to your network or to the internet.

claude.ai reaches a connector by address, and the address it asks for is public. Its own Add-custom-connector dialog describes the field as the HTTPS address where the server accepts MCP requests, of the shape https://mcp.example.com/mcp. A page in a browser cannot reach 127.0.0.1 on your PC, and it cannot start a program on it the way the desktop app can.

That is the whole difference between the three clients. Claude Code speaks to the loopback address itself, Claude Desktop starts a small program that does, and the browser can do neither.

What would change it: a relay

The missing piece is a relay: a small service on a public address that Creator dials out to, which then offers a public endpoint to claude.ai and forwards each request back down that same connection.

The design is built into Creator already, and the shape of it is worth knowing:

• Creator connects outward. No port is opened on your PC, and you install no tunnel software.
• You pair with a short code that Creator shows and you type on the relay’s consent page. It changes every few minutes and only works while Creator is running.
• The relay stores no map data. It forwards messages and remembers which PC a pairing points at.
• Every rule still applies. A request that arrives through the relay runs the same checks, the same token and the same confirm card as one from your own machine, so nothing changes your map without your click.
• UNPAIR is the kill switch. It drops the link, forgets the key this PC signs with and stops the local server in the same moment, so every credential the relay ever issued for that pairing stops working.
• The endpoint claude.ai would be given looks like this, and it is what you would paste into Customize > Connectors:

https://mcp.example.com/u/<pairing>/mcp

Caution

No relay is hosted for this alpha. Nothing is running at any address, so the relay field in Preferences > CONNECT is empty and there is nothing to pair with. PAIR is there for people who run a relay themselves, which is not a supported alpha path: you would need your own domain, your own certificate and your own deployment, and we cannot help you with any of it.

If a future release hosts a relay, this page gains the steps and the changelog will say so. ChatGPT is in exactly the same position and for the same reason.