Grok Bot: Vercel plugin (649) OAuth fails with “App configuration error – redirect URL is invalid”

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor for iOS

Describe the Bug

Grok Bot (iOS) — official Vercel marketplace plugin / MCP connector.

I cannot connect the official Vercel plugin (id 649) in Grok Bot. Starting auth opens Vercel’s authorize page and immediately shows:

App configuration error
The app redirect URL is invalid, please contact the app developer for support.

The connector stays needsAuth with 0 tools. This is the same Vercel error as the desktop thread, but this report is specifically for Grok Bot as requested.

Related desktop thread (deanrie asked for a separate Grok Bot thread here):

Steps to Reproduce

  1. In Grok Bot, install / open the official Vercel plugin (649)
  2. Tap Connect / authenticate the Vercel connector
  3. Grok Bot opens Vercel OAuth (vercel.com)
  4. Vercel shows “App configuration error – The app redirect URL is invalid”
  5. Auth never completes. Connector remains needsAuth, tools=0

Expected Behavior

OAuth should complete and the Vercel connector should become connected with tools available in Grok Bot, same as other official plugins.

Screenshots / Screen Recordings

vercel-mcp-error.png
vercel-mcp-error.png1320×2868 188 KB

Operating System

Other

Version Information

Client: Grok Bot iOS (App Store, Grok Bot 1.0). OS: iOS (iPhone), latest iOS. Plugin: Vercel official marketplace plugin, id 649. Connector status after failure: user-Vercel needsAuth, tools=0, detail=“Authentication required”. Other official plugins in the same Grok Bot session connect fine: Slack, GitHub, Figma, Sentry, Higgsfield, Context7, Supabase, Resend.

Additional Information

Screenshot attached (taken in Grok Bot iOS on vercel.com during the connect flow).

This matches Ahmet’s Aug 11 note on the desktop thread (plugin 649, Grok Bot, needsAuth / tools=0). Other OAuth plugins work in the same session, so this is isolated to Vercel’s authorize/redirect, not a general Grok Bot OAuth break.

Please whitelist Grok Bot / Cursor’s OAuth redirect URI on the Vercel MCP OAuth client (previously cited client_id=cl_KcWL599JrCOhI4n2lXPJJ8rkF4SqSbOf / cursor://anysphere.cursor-mcp/oauth/callback), or use a Grok Bot-compatible HTTPS redirect. Happy to ping Vercel support as well.

Does this stop you from using Cursor: No — Cursor / Grok Bot work, but the Vercel connector cannot be used from Grok Bot.

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Update: retrying Vercel plugin auth in Grok Bot now hits a different error page (looks like the Grok Bot / Cursor callback, not Vercel’s “redirect URL is invalid” screen):

OAuth callback failed.
Close this tab and try connecting again.

Screenshot attached. Connector is still needsAuth / tools=0 on plugin 649. Still cannot authorize Vercel in Grok Bot.

vercel-oauth-callback-failed
vercel-oauth-callback-failed2386×1584 95.7 KB

6

same issue, can’t connect vercel to Grok Bot

9

Hey all.

Thanks for the reports. We’re aware of an issue with Grok Bot and the Vercel Plugin (exactly as you’ve described, getting stopped at OAuth callback failed), and the team is looking into it!