ChatGPT on the web and Codex in the ChatGPT desktop app connect to MCP servers in different ways. Once connected, either can build and publish seating charts and run your events: prices, single-seat prices, sales, close times, channels, orders and reports. Neither books or sells seats for buyers, and neither can refund or charge anyone; see what the SeatLayer MCP covers.
The server URL is on Dashboard → Agent connections in SeatLayer. In
production it is https://mcp.seatlayer.io/mcp. For ChatGPT on the web, use
https://mcp.seatlayer.io/mcp?tools=build: it lists the 63 tools for
building, editing, pricing, checking and publishing, so each turn carries less
than half the tool definitions. Add ,trace to trace a floor-plan image. For
Codex, use the plain URL. See toolsets.
ChatGPT on the web
ChatGPT web does not read a local Codex config.toml. You add SeatLayer as a
custom MCP server in Plugins, on the web; the mobile app cannot add one.
- Open Plugins and choose + › Add custom MCP server. You don’t need to turn on Developer Mode first.
- Name it
SeatLayer, paste the server URL, choose OAuth, accept ChatGPT’s warning and create the plugin. Sign in to SeatLayer and approve it (see the consent screen below). - In a chat, type @ and pick SeatLayer.
On a personal account those three steps are all: we added SeatLayer from a Free account on 2 November 2026 and used it straight away, with nothing to publish.
On a Business, Enterprise or Edu workspace, an admin or owner adds it (on Enterprise and Edu, also a member an admin has allowed). An admin or owner then publishes it for the workspace from the Admin console under Plugins, and members find it under Plugins.
OpenAI’s help article lists which plans can add custom MCP servers, and that list can change. If you can’t find Add custom MCP server, use Codex or Claude instead.
ChatGPT desktop app with Codex
The desktop app’s Codex surface shares MCP configuration with the Codex CLI and IDE extension:
- Open Settings → MCP servers.
- Add a Streamable HTTP server named
SeatLayerwith the server URL. - Restart, choose Authenticate, and approve the grant in the browser.
- Run
/mcpto confirm the server is connected.
Follow connect Codex for the CLI setup and a safe first prompt.
The SeatLayer consent screen
Whichever client you use, SeatLayer shows the same screen, and the person approving needs the SeatLayer admin role. It is one tap: Allow gives the agent the workspace shown, with every permission below. Customize narrows it to one chart or turns permissions off. A workspace grant lets the agent list and create charts there.
Never paste a SeatLayer secret key into ChatGPT. The connection uses OAuth tokens that expire hourly and refresh on their own.
What you can tick
Building and publishing charts is always included. The other boxes all start ticked, so one tap on Allow gives the agent the whole workspace. To give less, open Customize on that screen: choose One chart, or turn any of these off:
- Manage live events: block seats, hold seats back, open or close sections.
- Create and run events: create, edit and copy events; open, close and reopen sales; set a close time; end an event.
- Set prices and releases: ticket prices, single-seat prices, releases.
- Manage sales channels: partner and sponsor seats, buyer links, partner report links.
- Look after orders: find orders, resend tickets, ask for a refund an admin approves.
- Read reports: sales, prices, door counts, the event’s History.
- Change seat categories: move seats to another category on an event that’s selling.
It asks you first
For an event on sale, the agent shows a plan and waits for your yes. A yes covers that plan only; if the seats change first, it plans again. A chart is published only after you approve its review. Your admins get one email about agent changes at most every 15 minutes per agent. History names the agent, and an agent’s chart publish can be undone in one click. Refunds need an admin: the agent can’t refund or charge anyone; it can ask, and an admin approves it in Orders.
Without a connection, ChatGPT can still write a Venue Spec for you to paste into the Designer.
Continue with SeatLayer MCP for the tool list and the chart and event workflows.