## **🔍 What This Article Covers**

If you previously connected Search Atlas to ChatGPT through MCP and the connection has stopped working — for example, ChatGPT no longer pulls your data or keeps asking you to sign in — this guide explains why it happens and how to restore the connection in a few minutes.

## **⚠️ Why the Connection Drops**

Search Atlas MCP uses OAuth 2.1 to authorize ChatGPT, and access tokens expire on a schedule for security. A dropped connection is usually temporary and easy to fix. Common causes include:

- **Expired token:** The authorization token between ChatGPT and Search Atlas timed out and was not refreshed automatically.
- **Stale bearer token:** A known issue can cause a **403 error** on our discovery endpoints when an old token is cached. A permanent fix is rolling out now; until it reaches your account, reconnecting manually is the reliable workaround.
- **Disconnected app:** The Search Atlas connector was removed in ChatGPT settings, either by you or by a workspace admin.
- **Account changes:** A password reset, plan change, or workspace switch on the Search Atlas side can invalidate an existing session.

## **🛠️ How to Reconnect Step by Step**

The fastest fix is to fully remove the old connection and authorize it again. Follow these steps:

1. Open ChatGPT and go to **Settings**.
2. Open the **Apps and Connectors** section (name may vary slightly by ChatGPT version).
3. Find **Search Atlas MCP** in your list of connected apps and select **Remove** or **Disconnect**. This clears the stale token.
4. Re-add the connector using the same Search Atlas MCP listing or server URL you used originally.
5. Complete the sign-in screen with your **Search Atlas account email and password** — use the same account you use inside the Search Atlas platform.
6. Approve the permission prompts to finish authorizing the connection.
7. Return to your ChatGPT conversation and test the connection using the steps below.

If ChatGPT shows a 403 error during the reconnect attempt, sign out of Search Atlas in your browser, sign back in, and repeat the steps above. This forces a fresh token to be issued.

## **✅ Confirm the Connection Works**

After reconnecting, verify everything is active:

- In ChatGPT settings, the Search Atlas connector shows a **Connected** status.
- Ask ChatGPT a simple question that requires your Search Atlas data, such as pulling details for one of your OTTO SEO sites or running a visibility check.
- If the tool responds with live data from your account, the connection is restored.

## **💡 Tips to Avoid Future Disconnects**

- Reconnect promptly whenever ChatGPT shows a sign-in or authorization prompt — delaying can leave a stale token in place.
- Use the same Search Atlas account in both the platform and ChatGPT to avoid session conflicts.
- Keep an active Search Atlas subscription; a lapsed plan can interrupt the authorization.
- After any password reset or workspace change, remove and re-add the connector to refresh the token.

## **🚀 Known Issue and Upcoming Fix**

Our engineering team is releasing a fix for the bug that causes 403 errors on stale bearer tokens during MCP reconnection. Once deployed, ChatGPT will refresh expired tokens automatically and manual reconnects should no longer be needed. Until the fix reaches your account, the remove-and-reconnect steps above will restore access every time.

## **🙋 Still Need Help?**

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type **human teammate** to be connected with a member of our team.