---
title: "Connect ChatGPT"
description: "Understand the difference between ChatGPT web plugins and local Codex MCP configuration before connecting SeatLayer Designer MCP."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.seatlayer.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect ChatGPT

ChatGPT web and local Codex clients use different MCP setup paths. OpenAI's
current [MCP documentation](https://learn.chatgpt.com/docs/extend/mcp) states
that ChatGPT web uses remote MCP-backed tools supplied by installed plugins,
while the ChatGPT desktop app's Codex surface, Codex CLI, and the IDE extension
can connect directly and share local MCP configuration.

## ChatGPT web

ChatGPT web does not read your local Codex `config.toml`. A SeatLayer tool must
be available through an installed workspace-approved plugin before Chat or Work
can use it.

SeatLayer Designer MCP is currently a chart-scoped Preview, not a promise that
a public SeatLayer plugin is available in every ChatGPT workspace. If your
workspace does not show an approved SeatLayer plugin, use a supported direct
remote-MCP client such as Codex or Claude instead.

## ChatGPT desktop app with Codex

Use the Codex MCP setup:

1. Open **Settings → MCP servers**.
2. Add a **Streamable HTTP** server using the URL from SeatLayer's
   **Dashboard → Agent connections**.
3. Restart, authenticate, and confirm the server with `/mcp`.

Follow [connect Codex](/agents/connect-codex) for the complete check and
[Designer MCP](/agents/designer-mcp) for chart-authoring rules.

> **Same product boundary in every client**
>
> The client supplies the model. SeatLayer still owns OAuth scope, permissions,
> chart writes, canonical revisions, validation, evidence, billing records, and
> publish confirmation.

Source: https://docs.seatlayer.io/agents/connect-chatgpt/index.mdx