Grok Bot
Fix Inkbox Unsupported redirect_uri on Grok Bot iOS
Fix Inkbox Unsupported redirect_uri on Grok Bot iOS
On Grok Bot iOS, the Inkbox catalog connect card can stop before OAuth with Couldn’t start sign-in: Unsupported redirect_uri. MCP status stays needsAuth for user-Inkbox (plugin id 57102943). Cursor staff (mohitjain) on Inkbox connect card fails with Unsupported redirect_uri said how to work around it when Inkbox is already authorized on desktop.
Prefer the desktop identity
- Confirm Inkbox was connected on Mac or Windows for the same Cursor account (shared connector account
default). - On iPhone, do not tap Connect on the Inkbox card when it shows Unsupported redirect_uri.
- Ask the Bot to use an Inkbox tool, or fully close and reopen the app, so it picks up the desktop identity.
Staff’s example: the identity authorized on desktop (their @solly-agent account) should carry to the phone for the shared default Inkbox connector.
If tools still fail on iOS
- Retry asking for an Inkbox action after a full app quit/reopen.
- Keep using desktop for Inkbox auth and heavy SMS/iMessage work until staff posts that the iOS connect path works on its own.
- Leave a short note on the staff thread if tools still fail after the desktop identity is present — staff said they are tracking the mobile connect flow separately.
Pitfalls
- Tapping Connect again on iOS for this symptom — the card never starts OAuth while redirect_uri is rejected.
- Treating Unsupported redirect_uri as a wrong Inkbox password or a broken desktop auth — staff put the failure on the mobile connect flow.
- Inventing a custom redirect URI or a hand-added MCP to “fix” the catalog plugin — not what staff recommended.