ChatGPT Remote MCP Connection Issues
When connecting ChatGPT to the Atlan Remote MCP server, you may encounter issues related to permissions, OAuth token state, or session configuration. This page covers the most common issues and how to fix them.
ChatGPT MCP returns empty results after connecting
The Atlan connector is connected but returned no results. This may indicate a permissions issue with your account.
Cause
Atlan MCP results are scoped to the authenticated user's persona. If no persona is assigned, or if an admin completed OAuth on behalf of the user, the session lacks data access.
Solution
- Confirm the querying user has an assigned persona in Atlan with access to the assets being queried.
- Test with a broad query—"how many tables exist in Atlan?"—to rule out a full access block.
- If using a shared connector set up by an admin, confirm OAuth completed for your own account, not just the admin's.
ChatGPT MCP OAuth loops with repeated permission requests
ChatGPT keeps redirecting to re-authorize after you've already approved.
Cause
Stale or conflicting OAuth tokens between ChatGPT and Atlan block the authorization flow from completing. Revoking and re-adding the connector without clearing the previous token state causes this loop.
Solution
- In ChatGPT, go to Settings → Apps & Connectors and disconnect the Atlan connector entirely.
- In Atlan, go to Admin Settings → API Keys / Tokens and revoke any OAuth tokens previously issued to ChatGPT.
- Reconnect from scratch and complete a fresh OAuth flow.
ChatGPT MCP OAuth fails on first attempt
We couldn't connect to this service. Authorization failed — please try again.
Cause
An expired or inconsistent ChatGPT session causes the OAuth redirect to fail before authentication completes.
Solution
Log out of ChatGPT, log back in to refresh your session, then retry the connector setup from Settings → Apps & Connectors.
See also
Need help
If you need assistance after trying these steps, contact Atlan Support.