## **💡 What these errors mean**

Search Atlas can connect to ChatGPT through OAuth and an MCP endpoint so ChatGPT can discover available actions. Two messages come up most often during setup.

- **Authentication succeeded, action discovery failed** means you signed in successfully, but ChatGPT could not load the list of actions from the MCP endpoint.
- **Missing OAuth callback data** means the return step from Search Atlas did not include the information ChatGPT needs to finish the connection. This often appears after switching to the Lite endpoint mid-setup.

Neither message means your Search Atlas account is broken. They usually come from an incomplete browser redirect, a mismatched endpoint, or a connection that was started twice.

## **🛠️ Before you reconnect**

- Use the same browser for Search Atlas and ChatGPT, and allow pop-ups for both sites.
- Sign in to the Search Atlas account you want ChatGPT to use.
- Pick one endpoint and stay with it for the whole attempt: the standard MCP endpoint or the Lite endpoint. Do not start on one and finish on the other.
- Close extra ChatGPT or OAuth tabs from earlier attempts so an old callback cannot overwrite the new one.

## **🚀 Reconnect from a clean start**

1. In ChatGPT, open the Search Atlas connection or custom action and disconnect or remove it if it is already listed.
2. Start a new connection and paste only the endpoint you intend to use.
3. When the Search Atlas sign-in window opens, complete login and approve access. Leave that window open until it closes on its own or returns you to ChatGPT.
4. Wait for action discovery to finish. If discovery fails once, wait a minute and choose retry or refresh actions before changing the endpoint.
5. Confirm the connection shows as connected and that actions are listed. Then run a simple request in ChatGPT to verify the link.

## **⚙️ If action discovery still fails**

- Confirm the MCP URL has no extra spaces, quotes, or a trailing path copied from a different setup guide.
- Stay on the endpoint that completed OAuth. Switching to Lite after a successful sign-in starts a different callback and often causes **Missing OAuth callback data**.
- Disable strict pop-up or tracking blockers for the sign-in window, then repeat the clean reconnect.
- Try a private or incognito window so an old ChatGPT or Search Atlas session cannot reuse a finished authorization code.
- Sign out of Search Atlas, sign back in, and start the ChatGPT connection again.

## **📊 Lite endpoint notes**

Use the Lite endpoint only when you specifically need that lighter action set. It is a separate connection, not a fallback you can open after the standard flow fails. If Lite reports missing callback data, discard that attempt, return to ChatGPT, remove the partial connection, and begin again using only the Lite URL.

## **💡 What support can and cannot see**

A successful sign-in does not guarantee that ChatGPT stored the callback or discovered actions. If you contact support, share the exact error text, whether you used the standard or Lite endpoint, the approximate time of the attempt, and the browser you used. Do not send authorization codes, tokens, or full callback URLs.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.