Codex can connect directly to a remote Streamable HTTP MCP server. The ChatGPT desktop app, Codex CLI, and Codex IDE extension share MCP configuration on the same machine. Once connected, Codex can build and publish seating charts and run your events: prices, single-seat prices, sales, close times, channels, orders and reports. It doesn’t book or sell seats for buyers, and it can’t refund or charge anyone; see what the SeatLayer MCP covers. OpenAI documents its configuration in its MCP documentation.
Desktop app or IDE
- Open Settings → MCP servers.
- Select Add server.
- Name it
SeatLayer, choose Streamable HTTP, and paste the URL. - Save and restart the app or extension.
- Select Authenticate. SeatLayer opens in your browser.
- Approve the grant on the SeatLayer consent screen (below).
- Use
/mcpto confirm that the server is connected.
CLI
Add the remote server to ~/.codex/config.toml or the trusted project’s
.codex/config.toml:
[mcp_servers.seatlayer]
url = "https://mcp.seatlayer.io/mcp"
auth = "oauth"
default_tools_approval_mode = "writes"Then run codex mcp login seatlayer to authenticate and codex mcp list to
check it. default_tools_approval_mode = "writes" keeps Codex asking before
any tool that changes a chart or an event. OpenAI documents the current
configuration keys and CLI commands in its MCP guide.
Do not place a SeatLayer secret API key in a prompt or configuration file.
The SeatLayer consent screen
The person approving needs the SeatLayer admin role. Allow gives the agent the workspace shown, with every permission below; Customize narrows it to one chart or turns permissions off.
Access tokens 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.
Verify safely
Start with a read and capability check:
Use the SeatLayer connector.
Call get_capabilities first, state the authorized chart or workspace, and
summarize the current chart. Do not change, approve, or publish anything.The reply should name the chart or workspace you approved and list the tools the grant allows. Then follow the staged workflow in SeatLayer MCP. Any write must use the current expected revision, and publishing still requires a human-approved unchanged revision.