Connect ChatGPT to Customer MCP
ChatGPT reaches Customer MCP by browser sign-in. It has no field for an integration key. Do not paste a key into ChatGPT, a custom GPT, or a chat.
Browser sign-in works only while MCP_OAUTH_TENANT_ENABLED is 1. On this tdev machine that flag is 1. While it is 0, ChatGPT cannot connect, and Claude Code with an integration key is the path that still works.
When browser sign-in is on
The public URL is https://<tenant-host>/mcp. On this tdev machine the test tenant is https://conpds-test.tdev.conpds.com/mcp. Do not use the admin host.
In ChatGPT, a workspace owner turns on developer mode, then creates an app:
- Open Settings → Apps. Turn on Developer mode under advanced settings. A workspace may instead use Workspace settings → Permissions & Roles.
- Choose Apps → Create.
- Name the app, for example
ConPDS Customer. - Set the MCP server URL to
https://<tenant-host>/mcp. - Choose OAuth. Leave the client secret empty. ChatGPT registers itself. Do not type a guessed callback address. If ChatGPT shows a callback URL, leave it as shown.
- Start the tool scan and finish the sign-in in the browser. Sign in to the tenant, then on Authorize connector check the request (see below), choose one of your integration keys, and choose Authorize. ChatGPT receives that key's capabilities and terminal scope. It does not receive the key secret. If the page says no integration key is available, create one under Admin → Integration keys and start the scan again.
- Create the app.
Check the request before you authorize
Authorize connector shows what the app asked for. Check it before you choose Authorize:
- Returns to is the site that receives the authorization. It must be the app you are connecting, for example a ChatGPT address. If you do not recognise it, close the page.
- Name given by the app (not verified) is whatever the app typed when it registered. ConPDS does not check it, so do not rely on it. Not provided means the app gave no name.
- Requested scopes must match what you expect the app to use.
If the page says This authorization request has expired or is missing, start the connection again from the app. Authorize stays disabled until a live request is shown.
To remove a connector later, use Connected apps.
In a new chat, enable the app and ask for whoami. The answer should name the tenant, the timezone, and the MCP capabilities. It should not include a key.
The server accepts one JSON request at a time. A message about an event stream or “Not Acceptable” does not by itself mean sign-in failed. Check whether whoami still answers.
What this connector cannot do
- It cannot use a tenant integration key or an Ops service key.
- It is not Ops MCP. Operator data uses the admin host and a separate app.
- It cannot read picture bytes or message bodies.