Troubleshooting
MCP connector troubleshooting.
OAuth loops, workspace and site scoping, shared usage limits, and allow-listing the provider IP ranges.
Common issues
Fix it fast
Try signing in again first — a stale session on either side is the most common cause. If it keeps looping, remove the SearchChamp connector from your AI app entirely, add it back with the connector URL from Settings → Connect your AI apps, and complete sign-in fresh.
This is usually a stale client-side cache rather than a real connection problem — the AI app cached the connector's tool list before you finished setup. Remove and re-add the connector, or start a brand-new conversation; either forces the app to re-fetch the current tool list from SearchChamp.
Remove it from your AI app's connector list (Claude: Settings → Connectors; ChatGPT: Settings → Connectors), and separately revoke access from SearchChamp under Settings → Connect your AI apps. Revoking from the SearchChamp side immediately invalidates the connection even if the AI app still lists it.
Immediately on the SearchChamp side — revoking from Settings → Connect your AI apps invalidates the connection instantly, not on a delay. The AI app itself may keep the connector listed in its UI until you remove it there too, but any tool call it attempts after revocation will fail.
Still stuck?
Talk to our team.
Include your workspace URL, which AI app you’re connecting, and the exact error message you saw — that’s usually enough for us to spot the cause without a back-and-forth. Expect a reply within one business day; check the response-time table on the contact page for your plan’s SLA.