ChatGPT follow up call silently switched connectors
The point
With two connectors enabled for the same MCP server, ChatGPT called a confirmation tool through connector A. Its follow up call, carrying a one time confirmation code, went silently through connector B instead. The server rejected it because the code was bound to connector A OAuth client.
Why it matters
For builders, a workflow must keep its starting connector and OAuth grant.
Key details
- Each connector has its own OAuth client, even when both share the same MCP server URL
- The reporter warns the switch could pass one app data to another provider
Original ~4 min → 25 sec here Source: OpenAI Developer Community, Nov 5, 2026