MCP connector troubleshooting.
OAuth loops, workspace and site scoping, shared usage limits, and allow-listing the provider IP ranges.
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.
The connector shares your existing in-app usage quotas rather than having a separate allowance. Some actions also require your explicit approval before they run, which shows up as a confirmation step rather than a hard block.
Usually it means the site or date range you asked about doesn't have data yet, or your account doesn't have access to that site. Rephrase the request with the exact domain, or check that the site is set up correctly in your SearchChamp workspace first.
Confirm the connector URL from Settings → Connect your AI apps was pasted in full and hasn't been edited, then try reconnecting — a truncated or stale URL is the most common cause. If it persists after a fresh reconnect, it's likely a transient outage on the AI provider's side rather than the connector itself; retry in a few minutes.
You choose your organization when you sign in during setup. From there, every tool call is scoped to the sites your account can access — the connector never returns data for a site outside your own permissions, and it can't be redirected to one.
Yes. Requests to the SearchChamp connector originate from the AI provider's own cloud infrastructure — Anthropic's for Claude, OpenAI's for ChatGPT — not from your device or office network. If you restrict inbound or outbound access, allow-list those provider ranges rather than a specific IP.
Allow-list by the provider's published range (Anthropic's or OpenAI's), not a specific IP you observed once — providers rotate addresses within their published ranges without notice, and pinning to one IP will eventually break the connection when it changes.
Each sign-in scopes the connector to one organization at a time. To work across multiple workspaces, sign in again and choose the other organization — most AI apps let you add SearchChamp as a second, separately-configured connector rather than switching back and forth on one.
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.