Connect ChatGPT

ChatGPT cannot drive Creator in this alpha. That is the whole answer, and the rest of this page is why, what would change it, and which clients do work today.

If you want an LLM driving your editor right now, use Claude Desktop or Claude Code. Both run on your own machine, both work, and both have a page that takes you through the setup.

Why it cannot

Creator’s server and ChatGPT want opposite things from an address.

Creator’s server	What ChatGPT accepts
Listens on 127.0.0.1, your own machine only. No port is opened to your network or to the internet.	A public HTTPS address. Its own connector documentation asks for “the MCP server URL, including the /mcp path”, and says a production server needs a stable, publicly reachable HTTPS endpoint.
Exists only while Creator is open, with a token that changes at every start.	A connector you add once and keep.
Can also be reached by a small program that a client starts on your PC, which is how Claude Desktop connects.	No way to start a local program. There is no stdio option.

So there is no address you can paste into ChatGPT that reaches your PC, and no local program it can launch instead. This is not a setting you have missed.

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 your LLM client and forwards each request down that same connection.

That design is already built into Creator, and it is worth knowing what it does and does not do:

• Creator makes an outbound connection. 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. The code 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. There is no path into a tool that skips them.
• The endpoint the client is given looks like this, and it is the address you would paste into ChatGPT’s connector settings:

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

Caution

No relay is hosted for this alpha. Nothing is running at any address, so the 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.

The other path, and why it is not the answer either

OpenAI ships its own outbound tunnel for reaching a private MCP server, meant for building and testing rather than for distribution: it needs a developer-mode app and an OpenAI Platform account, and it cannot be handed to other people. Creator ships no tunnel client, so this is not a path you can follow with what is in your download. It is here so you know it exists and know it is not the shape of an answer for a map editor you installed.

What works today

Client	Works with this alpha?	Page
Claude Desktop	Yes, on your own PC	Connect Claude Desktop
Claude Code	Yes, on your own PC	Connect Claude Code
claude.ai in a browser	No, it needs the relay	Connect Claude in your browser
ChatGPT (browser or desktop app)	No, it needs the relay	this page

If a future release hosts a relay, this page gains the steps and the changelog will say so.