Official X plugin auth is broken on Cursor Cloud, Grok Bot, and desktop refresh

Support Bug Reports
, , , ,
1

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

I cannot use the official X plugin (id 49086599) from Cursor or GrokBot, even with a funded X account.

Account

  • X console: @heyheathbar
  • Funded: $25.00 credits, $0 usage last 30 days
  • Surfaces: Cursor Cloud Agents, Grok Bot (custom_name), Cursor desktop

This is a Cursor OAuth/MCP auth bug, not an X credits or account-setup issue.

1. Cloud Authenticate uses the wrong callback

  • Plugin shows Needs Authentication in Cloud. The in-app Authenticate button fails every time.
  • X page: Something went wrong — You weren’t able to give access to the App.
  • Cursor still sends a desktop redirect on a Cloud login:
redirect_uri=cursor://anysphere.cursor-mcp/oauth/callback
state.kind=cloud-mcp
client_id=NGdZYmo4VVp2T1BnRG55NlExOGQ6MTpjaQ

X rejects that cursor:// callback. Retrying the same URL always fails. Cloud Agents also cannot run interactive MCP auth (Interactive MCP authentication is only available in the Cursor desktop IDE).

2. Grok Bot reports connected but has no tools

  • custom_name: X [connected] · account="default" · tools=0
  • Then: Namespace user-X not found
  • Cannot look up a handle (e.g. @rustybrick)

3. Desktop sign-in works, then Cursor drops the token

  • MCP OAuth tokens persisted / callback exchange completed / connected
  • Also: MCP OAuth credentials cleared (local housekeeping) → back to needsAuth
  • ~6 minutes later, refresh fails:
    • MCP OAuth SDK refresh catch branch
    • MCP OAuth refresh error
    • Value passed for the token was invalid
    • connection → failed

Ask
Fix Cloud/Grok Bot OAuth so it uses a callback X accepts (not cursor://… on kind=cloud-mcp), keep desktop refresh tokens valid, and expose X tools after connect (tools>0, user-X namespace available).

Steps to Reproduce

not sure seems to be with my specific account linkage, not an overall system bug. I don’t have another account “paid” to test against.

Expected Behavior

I should be able to connect a plugin on either Cursor or GrokBot, out of the box.

Screenshots / Screen Recordings

Screenshot 2026-08-26 at 5.38.44 PM.png
Screenshot 2026-08-26 at 5.38.44 PM.png638×514 22.7 KB
Screenshot 2026-08-26 at 5.32.41 PM.png
Screenshot 2026-08-26 at 5.32.41 PM.png433×213 10.1 KB
Screenshot 2026-08-26 at 5.21.39 PM.png
Screenshot 2026-08-26 at 5.21.39 PM.png662×379 6.5 KB

Operating System

MacOS

Version Information

Version: 3.17.21 (Universal)
VS Code Extension API: 1.128.0
Commit: 8f2a112cb2845a97b75fd932ea5c470579ca4060
Date: 2026-08-25T01:05:08.089Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 24.6.0

GROK BOT
Version: 0.27.0
Release Track: stable
OS: darwin

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

Hey @HeyHeathbar
This isn’t a credits or setup problem on your end. The failed connect, “connected but tools=0”, and the desktop connection dropping after a few minutes are all coming from our side.

This is an issue we’re tracking across desktop, Cloud, and Grok Bot, and part of it involves the X-side app config we’re working through. One note: the Cloud Agents message you saw is expected - agents can’t do an interactive sign-in themselves; the plugin is meant to be connected from the desktop app or dashboard and then shared to your cloud agents. I won’t pretend there’s a clean workaround right now, though, since the connect/refresh itself is the issue.

No timeline yet, but I’ll follow up here once X connections are holding again.

8

Any update on this?

9

I’m seeing the same issue with the official X plugin in Grok Bot on iOS.

Device: iPhone
Product: Grok Bot iOS
Plugin: official X plugin (X MCP)

Initial error:
“X is connected, but this account isn’t ready yet. Please remove and reinstall the X connection, then reconnect.”

What I tried:

  • Uninstalled and reinstalled the X plugin.
  • Reconnected the X account.
  • Added a second connection profile.

Current state:

  • Both profiles (“default” and “moje”) are shown as Connected.
  • The plugin now shows: “Failed to load connector” / “Nie udało się wczytać łącznika”.
  • The Authenticate button does not successfully complete authorization.
  • The plugin cannot be used; it appears to be connected but the MCP tools are not loading.

This looks like the connected-but-tools=0 / OAuth-MCP provisioning issue described in this thread.
I can provide screenshots if needed.

10

has there been any progress solving this issue?