OAuth connect fails or loops when adding the MCP connector
Symptom
When you add the prompt2love MCP connector in your AI client, the OAuth step fails, the consent screen reappears in a loop, or you see a redirect mismatch error.
Cause
- You aren't logged into prompt2love in the same browser the OAuth flow uses, so consent can't bind to your account.
- A stale connector from a previous attempt is interfering with the new authorization.
- The authorize request was interrupted (closed tab, timeout) before it completed.
Fix
- In a normal browser tab, log into prompt2love.com first. Keep that session open.
- Remove any stale connector for prompt2love from your AI client, then add it fresh.
- Retry the authorize step. When the prompt2love consent screen appears, click Authorize / Allow and let it redirect fully back — don't close the tab early.
- If consent keeps looping, clear cookies for prompt2love.com, log in again, and re-run the authorization.
- Make sure no aggressive pop-up blocker or privacy extension is cancelling the redirect.
The connector URL must be exactly https://prompt2love.com/api/mcp — a typo or trailing path can cause a redirect mismatch.
Still stuck?
If authorization still fails, see connect via ChatGPT for the full connector setup, or ask in the community with the exact error text you see.