I just upgraded to Lifetime, but when trying to OAUTH through the MCP get directed to a 404 page on https://threeui.com/oauth/consent?authorization_id=<id>, changing the url to https://threeui.netlify.app/oauth/consent?authorization_id=<id> renders a page, but unable to authenticate through it gives "unauthorized request origin".
```
ThreeUI needs to do one of the following:
- Change its Supabase Site URL to https://threeui.netlify.app and allow that origin; or
- Properly deploy/proxy /oauth/consent on https://threeui.com.
```
Thanks for reporting this — the OAuth consent route on the canonical domain is fixed and live now.
I just re-tested a fresh production OAuth request. It redirects to `https://threeui.com/oauth/consent`, loads the consent screen, recognizes a signed-in Pro member account, and reaches the **Authorize client** step without the 404 or `unauthorized request origin` error.
Please retry the MCP connection from scratch and keep the `threeui.com` URL unchanged. If an older authorization tab still fails, restart the connection so the client receives a fresh `authorization_id`.
If it still does not work, please reply with the MCP client name and the approximate time of the attempt. Please do not post the `authorization_id` publicly.
Closing this since the production OAuth route remains fixed and we haven’t received any further report after the retry request. If the problem is still happening, please reopen the issue and include the MCP client name and approximate time of the attempt. Please do not post the `authorization_id` publicly.