Connecting to ChatGPT and Codex

Use this guide to connect ChatGPT and Codex to PropampAI MCP. The ChatGPT desktop app includes Chat, Work, and Codex in one app on macOS, Windows, and Linux. The Codex CLI and the Codex IDE extension share MCP settings with that app.

ChatGPT on the web uses a separate plugin. A server you add only in the desktop app is available on that computer. A plugin you add only on the web is available in ChatGPT on the web.

The desktop app, the CLI, and the IDE extension read the same user config file, ~/.codex/config.toml. Set the server up in any one of them. If CODEX_HOME is set, the file is $CODEX_HOME/config.toml.

OpenAI documents this layout in Model Context Protocol  and Moving to the ChatGPT desktop app .

Before You Start

1. Confirm Seller Central is connected in PropampAI and the first sync has finished. See Prerequisites.
2. Sign in to ChatGPT. For the desktop app, install it and sign in. If you still have the older Codex app, update it. After the update it is the ChatGPT desktop app, and it opens in Codex for existing Codex users. Setup for the app is in the ChatGPT desktop quickstart .
3. Keep this MCP endpoint ready:

https://mcp.propamp.ai/mcp

Note: Use that exact URL. PropampAI MCP speaks Streamable HTTP on /mcp. The older https://mcp.propamp.ai/mcp/sse address is a legacy transport, and ChatGPT and Codex connect with Streamable HTTP.

PropampAI authenticates with OAuth. You sign in with the same email and password you use on the PropampAI web app, on a PropampAI page. There is no API key, client ID, or client secret to paste. Your password stays on that PropampAI page. ChatGPT and Codex receive a token. See Data & Permissions.

Add the Server in the ChatGPT Desktop App

This is the setup for Chat, Work, and Codex on your computer. It also fills in ~/.codex/config.toml for the CLI and the IDE extension.

1. Open Settings, then select MCP servers. You can also press Cmd+, on macOS or Ctrl+, on Windows.
2. Select Add server.
3. Name the server propamp. That name is the id in config.toml, and it is the name you pass to codex mcp login.
4. Choose Streamable HTTP.
5. URL: https://mcp.propamp.ai/mcp.
6. Save the server, then select Restart.

The server list shows which servers are enabled and which require OAuth. Select Authenticate for propamp. A PropampAI sign-in page opens in your browser. Enter your PropampAI email and password, then return to the app.

In the composer, type /mcp to see connected servers.

If the form shows header fields, leave them empty. The OAuth sign-in is the authentication. Choose Streamable HTTP and enter the URL. A local command starts a STDIO process on your computer. PropampAI is a remote server, so the URL is what connects it.

A trusted project can also define MCP servers in .codex/config.toml inside that project. Codex loads the project file for a trusted project. The Settings screen writes the user-level ~/.codex/config.toml.

Approve Tool Calls

When a PropampAI tool can change data, approve the call when ChatGPT or Codex asks.

On the desktop app, the CLI, and the IDE extension, default_tools_approval_mode under the server sets the default. OpenAI accepts auto, prompt, writes, and approve. writes asks before tools that are not marked read-only:

[mcp_servers.propamp]
url = "https://mcp.propamp.ai/mcp"
default_tools_approval_mode = "writes"

On ChatGPT web, the prompt follows the plugin’s app permissions and the action. Confirm the action when ChatGPT asks. Details are in Connecting custom MCP servers in ChatGPT .

Add the Server with the Codex CLI

The Codex CLI is its own install, and it reads and writes the same config.toml as the desktop app. Use this section for the terminal commands, including when the desktop app is not installed.

Install the CLI, then sign in to ChatGPT with codex login. That login is your ChatGPT account. The PropampAI login is a second step, codex mcp login propamp.

macOS and Linux:

curl -fsSL https://chatgpt.com/codex/install.sh | sh

Windows PowerShell:

irm https://chatgpt.com/codex/install.ps1 | iex

When Node.js is already installed, OpenAI’s CI examples install the same CLI with npm install --global @openai/codex.

Add the server and start the PropampAI sign-in:

codex mcp add propamp --url https://mcp.propamp.ai/mcp
codex mcp login propamp

codex mcp login works for Streamable HTTP servers that support OAuth. PropampAI supports that login. PropampAI publishes a registration endpoint, and Codex registers itself during login. The two commands above are the full setup. The browser opens the PropampAI sign-in page. Enter your PropampAI email and password, then return to the terminal when it confirms the login.

To edit the file yourself, save this block and then run codex mcp login propamp:

[mcp_servers.propamp]
url = "https://mcp.propamp.ai/mcp"

In the Codex terminal UI, type /mcp to see active MCP servers. codex mcp list prints the servers saved in config.toml.

Static Bearer Token

OAuth is the login to use. If you already have a PropampAI access token and want the CLI to send it on every request, point the server at an environment variable:

codex mcp add propamp --url https://mcp.propamp.ai/mcp --bearer-token-env-var PROPAMP_MCP_TOKEN

Or in config.toml:

[mcp_servers.propamp]
url = "https://mcp.propamp.ai/mcp"
bearer_token_env_var = "PROPAMP_MCP_TOKEN"

Export PROPAMP_MCP_TOKEN in the shell that starts Codex. The server expects that value as Authorization: Bearer. Access tokens expire, so run codex mcp login propamp when you can use OAuth.

Add the Server in the IDE Extension

The Codex IDE extension uses the same config.toml. A server you already added in the desktop app or the CLI is already there. To add it from the extension:

1. Open the gear menu, then select MCP servers.
2. Select Add server.
3. Name: propamp. Choose Streamable HTTP. URL: https://mcp.propamp.ai/mcp.
4. Save the server, then select Restart extension.
5. Select Authenticate when the list shows that propamp requires OAuth, and finish the PropampAI sign-in.

Add the Server in ChatGPT on the Web

ChatGPT on the web stores this connection as a plugin on your account or workspace. Hosted Work chats use plugins for remote MCP tools. A Codex cloud task runs off your computer, so the servers in ~/.codex/config.toml can be unavailable there. Add this plugin when you need PropampAI in a hosted chat. The desktop MCP servers list applies to the desktop app, the CLI, and the IDE extension on that computer.

Full MCP support on the web, including tools that modify data, is available for ChatGPT Business, Enterprise, and Edu. A Pro account can connect a custom MCP server for read and fetch tools. Custom MCP servers are added in the browser. OpenAI’s help article says this connection is not available in the mobile app.

On Enterprise, an admin grants Create plugins with MCPs before a member can add an MCP server. That permission is off until they grant it. On Business, admins and owners create the custom MCP plugin.

In the current Plugins flow you accept a risk warning for the server. Developer mode belongs to the older Apps → Create screen, covered at the end of this section.

1. Go to Plugins.
2. Select the plus button, then select Add custom MCP server.
3. Name: PropampAI MCP. Add a description if you want one.
4. Under Connection, enter https://mcp.propamp.ai/mcp. Leave Tunnel empty. PropampAI is already a public HTTPS endpoint.
5. When the form asks for authentication, choose OAuth. If it shows a client ID, a client secret, or headers, leave those empty. PropampAI publishes its OAuth metadata, and ChatGPT registers itself, then opens the PropampAI sign-in page.
6. Review the risk warning and select I understand and want to continue.
7. Select Create as a plugin, then review the tools and metadata ChatGPT discovered.
8. Install the plugin. Start a new chat, type @, and select the plugin.

Finish the PropampAI sign-in when ChatGPT opens it. Confirm a write action when ChatGPT asks.

To publish the plugin for a Business, Enterprise, or Edu workspace, an admin or owner publishes it from the admin console: Plugins → Manage Legacy Apps → Drafts → Publish. Members then find it under Settings → Plugins.

If Your Workspace Still Uses Apps → Create

That older screen uses Developer mode.

A workspace admin turns Developer mode on under Workspace Settings → Permissions & Roles → Connected Data Developer mode / Create custom MCP connectors.

• Business: each admin or owner enables it for themselves from Workspace settings → Apps → Create.
• Enterprise and Edu: after an admin grants access, open Settings → Apps → Advanced Settings and turn Developer mode on.

Then create the app from Apps → Create. Enter https://mcp.propamp.ai/mcp, choose OAuth when the form asks for an authentication mechanism, select Scan Tools, finish the PropampAI sign-in, and select Create. The draft appears under Apps → Drafts in workspace settings, or under Settings → Apps → Enabled Apps with a Dev label in user settings.

Verify the Connection

Desktop app

1. Open MCP servers and confirm propamp is enabled.
2. Type /mcp in the composer and confirm the server is connected.
3. Ask for live data, for example: “List my available products in the US marketplace.”
4. If the assistant calls a PropampAI tool and returns real data, setup is complete.

IDE extension

1. Open MCP servers and confirm propamp is enabled and authenticated.
2. Ask the same product question in a Codex chat.
3. Real product data means setup is complete.

CLI

1. Run codex mcp list and confirm propamp is listed.
2. Start codex, type /mcp, and confirm the server is active.
3. Ask the same product question. Real product data means setup is complete.

ChatGPT on the web

1. Confirm the plugin is installed.
2. In a new chat, select it with @.
3. Ask the same product question and confirm the action if ChatGPT asks.
4. Real product data means setup is complete.

Troubleshooting

• 401 Unauthorized — the client has no valid PropampAI token. In the desktop app or IDE extension, select Authenticate on propamp. In the CLI, run codex mcp login propamp. On the web, reconnect the plugin and finish the sign-in. A 401 on the first request, before any sign-in, is how the server tells the client to start OAuth.
• ChatGPT on the web asks you to sign in again later — PropampAI’s discovery document lists the scope mcp:tools and the refresh_token grant. It does not list offline_access. ChatGPT on the web can require a new sign-in after the access token expires. Open the plugin and complete the PropampAI sign-in again.
• 404 partway through a session — an idle session expired after 60 minutes. The server responds with “Session not found or expired. Send a new initialize request to start a session.” Start a new chat if the client does not reconnect on its own.
• 403 Authorization token does not match the active session — the request used a different token from the one that opened the session. Start a new chat so the client opens a new session.
• Server not found, or an SSE error — set the URL to https://mcp.propamp.ai/mcp, with no /sse suffix and no trailing slash, and choose Streamable HTTP.
• The server is missing after you save it — select Restart in the desktop app, or Restart extension in the IDE. Then select Authenticate if the list still asks for OAuth.
• You edited config.toml and nothing changed — confirm the file is the one in your Codex home. The default path is ~/.codex/config.toml. When CODEX_HOME is set, edit $CODEX_HOME/config.toml instead. Restart the app or the CLI after you save.
• No tools appear — Seller Central may still be syncing, or the organization may need the MCP access add-on. See Troubleshooting. On ChatGPT web, a Pro account receives read and fetch tools. Write tools require Business, Enterprise, or Edu.
• A billing message instead of data — external MCP access is not enabled for your organization. Email [email protected].
• The web form will not create the plugin — on Enterprise, ask an admin to grant Create plugins with MCPs. On Business, an admin or owner has to create it. Developer mode is part of the older Apps → Create screen. The Plugins → Add custom MCP server screen uses the risk checkbox instead.
• Sign-in fails with HTTP 429 — the OAuth endpoints are rate limited. Wait for the Retry-After interval, then run the sign-in again.
• Your network blocks the endpoint — allow outbound access to mcp.propamp.ai, or test from another network.