Grok BotGuide

Plugins

Grok Bot plugin OAuth failed

Grok Bot plugin OAuth failed when the browser tab never finishes, or the plugin says Connected and still exposes no tools. Reopen the authorization tab and finish it with the account you meant. Do not paste a bearer token into chat.

Connectors are stored on the Cursor account, not on one Bot. A second click on Connect often stacks a new attempt on a login that is already half saved.

Plugins lesson: connectors before the browser

Why the native method fails

The native method is Connect again, then Reset the computer when the spinner survives. Reset rebuilds the hosted machine. It does not clear an OAuth record. Notion is the documented case: staff say the sign-in lives on the account, so retrying Connect fails, and Re-authenticate is the control that clears it. Zoom error 4700 is not a setting you own. The catalog plugin hard-codes the callback as http://localhost:8787/callback. Zoom rejects the hostname localhost. Official Help says there is no user workaround until that redirect moves off localhost. Editing a Zoom app in your own developer console does not change the catalog callback.

A team admin can also turn marketplace plugins off. The label is Disabled by team admin. That is policy, not a bad redirect, and another Connect click will not override it.

Steps

  1. Open Marketplace from the sidebar, then Your plugins, and confirm the plugin is under Installed. On the phone, tap the top-left avatar, then Plugins. Official troubleshooting starts here.
  2. Reopen the plugin detail and choose the authentication action. If the app says Waiting for authorization, use Reopen so the browser tab comes back. Keep Grok Bot open while the browser finishes.
  3. Complete the browser prompt with the intended account. Return to Grok Bot and retry the task. If the source service revoked access, remove the plugin and connect it again.
  4. Check whether the connector wants an organization variable or an administrator setting. A finished OAuth screen can still leave the tool dark when that value is missing.
  5. Notion Invalid redirect_uri: use Re-authenticate, not Connect again.
  6. Gmail: staff say the Grok Bot plugin OAuth path is broken. Authorize Gmail from Cursor. That path is different, and the connection is shared into Grok Bot until the plugin is fixed.
  7. GitHub that shows Connected but fails with Authorization header is badly formatted: press and hold the account, choose Remove, then sign in again. That is the staff workaround for a tracked bug.
  8. Canva Invalid redirect URI on iPhone: staff call it an app-link versus web-redirect mismatch, not your Canva settings. Connect Canva from desktop Grok Bot on the same account. The connector syncs to the phone.
  9. Official X plugin: staff say connect and refresh fail across the Cursor desktop, Cloud Agents, and Grok Bot, including Connected with tools equal to zero. There is no clean workaround in that note while X-side app configuration is fixed. X login risk controls on the cloud computer are a separate, known phenomenon. They are not proof the Cursor account is broken.

Limits

The Gmail connector can list attachment metadata and still have no tool that downloads the bytes. Staff say to use the cloud browser or park the file in Drive. Drive itself is file-level. Editing a Google Doc body or Sheet cells is the separate Docs or Sheets connector, added from the marketplace on the same Google account.

The Phantom plugin runs on its own MCP server. Staff say each new authorization creates a separate dedicated agent wallet, not your personal Phantom wallet. A reconnect can show a new address while funds stay on the old agent wallet. Recover that from chat history or through Phantom support. Connecting again on purpose to “get the old address back” creates another wallet.

There is no settings form for a custom connector. Tell the Bot in chat to add an MCP server that is public HTTPS, streamable HTTP or SSE, confirm the details, and the tools show up on the next message. An MCP that only listens on localhost on your PC is unreachable from the cloud computer. Local stdio MCP is the same refusal.

Zoom 4700 and the broken X plugin are waiting on the vendor side. This page will not invent a redirect host or a header format for you to paste. Secrets belong on the official secrets card, masked, out of the transcript.

FAQ

The plugin says Connected. Why are there no tools?

Connected only means an auth record exists. Staff have seen the official X plugin report Connected with zero tools, and GitHub report Connected with a badly formatted Authorization header. Remove and sign in again for GitHub. X has no clean workaround in the staff note.

Should I Reset the computer because Gmail will not connect?

No. Reset changes the computer. Gmail staff guidance is to authorize Gmail from Cursor so the shared connection is available to Grok Bot. Reset will not repair that OAuth path.

Can I fix Zoom error 4700 in my own Zoom app?

No. Official Help says the catalog callback is hardcoded to localhost and Zoom rejects it. There is no user-side workaround until the redirect changes.

Canva works on my Mac and fails on my iPhone. Which settings do I change?

None on the Canva side, according to staff. Connect Canva once from desktop Grok Bot on the same Cursor account. The connector then syncs to the phone.

Are plugins private to one Bot?

No. Installed connectors are account-level. Authorizing GitHub for one Bot leaves it available to later Bots on that account.

Related

Sources

  • Official troubleshooting
  • Connect plugins
  • Notion redirect
  • Gmail plugin
  • Gmail attachment bytes
  • GitHub header
  • Canva on iOS
  • X plugin