Fix MCP connection issues
Most connector issues are OAuth consent, wrong project scope, or a stale client cache — not a down MCP endpoint.
What symptoms show up?
- OAuth window closes without access.
- Assistant cannot see the expected project or rivals.
- Tools error after a teammate left or a project was renamed.
- Claude directory connect works but ChatGPT connector fails (or the reverse).
- Gemini, Cursor, Notion, or PostHog never finishes OAuth after you add https://api.spiderlook.com/mcp.
How do I fix it step by step?
Re-run Connect your AI from Settings → AI agents and complete /oauth/authorize. Confirm the authorized project is the landscape you expect. For Claude, prefer the directory listing at https://claude.ai/directory/spiderlook. For ChatGPT and other clients, confirm the server URL is https://api.spiderlook.com/mcp and that you did not paste a bearer token.
- Revoke the stale connector in the client, then reconnect.
- Retry OAuth and pick the correct project.
- Call list_workspace before other tools.
- If Claude fails, retry via the directory; if ChatGPT or another client fails, recreate the custom MCP server entry.
What if I am still stuck?
Confirm the user can open the project in the Spiderlook app with the same login. MCP cannot expose projects the user cannot access in-app. Check plan activation and that the organization still has usage for tool calls that burn allowance.
If OAuth loops, clear the client’s MCP auth cache, disable VPN blockers for app.spiderlook.com and api.spiderlook.com, and retry once with a fresh browser session.
How do fixes differ by client?
Claude: retry via https://claude.ai/directory/spiderlook, then list_workspace. ChatGPT: delete the custom connector, recreate with https://api.spiderlook.com/mcp, and finish OAuth without a bearer token.
Gemini, Cursor, Notion, PostHog, and any other client that supports MCP: remove the remote server entry, re-add the same URL, and complete OAuth again. If the client caches auth, clear MCP authentication in that client’s settings before retrying.
Across clients, confirm the Spiderlook user can open the project in-app. MCP cannot expand access beyond the signed-in user’s organization and project permissions.