AgentGrok Bot connector not working? Fixes for apps, custom MCP servers and lost connectors
A Grok Bot connector not working usually comes down to one of four things: the app is installed but not signed in, a custom MCP server can't be reached or rejects the sign-in, your accounts were combined and the setup stayed behind, or the bug is on SpaceXSI's side. This guide sticks to connectors and MCP servers, using the Grok Bot docs from SpaceXSI (formerly xAI), read November 13, 2026. For usage limits, a stalled Bot or one that never wakes, see Grok Bot not working.
Quick answer
Open Connect apps and check the app's status. Added only means installed. If it shows Needs auth or Disconnected, choose Authenticate and finish signing in within about 10 minutes. Still broken? Remove the app, add it again and sign in. If connectors vanished after you unified accounts, add your custom MCP servers again on the primary account.
How do Grok Bot connectors work?
They're apps, or custom MCP servers, that every Bot on your account shares after one sign-in.
A Grok Bot gets its outside tools from Connect apps in the sidebar (on the phone, tap your picture, then Connect apps). You can add an app from the catalog, ask a Bot to do it ("Add the Linear app"), or bring your own server: at the bottom of Connect apps, choose Add a custom connector, name it, then pick Remote HTTPS (a server address, with optional HTTP headers and an OAuth client ID) or Command (a program that runs on the Bot's computer), and choose Add plugin. MCP, short for Model Context Protocol, is the shared standard those servers speak. Connectors in the Grok chat app at grok.com are a separate setup, covered in custom connector not working.
Four details from SpaceXSI's docs explain a lot of strange behavior:
- Apps belong to the account. Every Bot you run can use them, on any device, but only under the account you signed in with.
- The Bot never holds your logins. Sign-in tokens sit on Cursor's connector service, and the Bot calls tools without seeing them.
- Private servers need your OK. A server on a private network, or one with a private certificate, asks for your approval before it's added.
- Team rules win. An app your team blocks shows Disabled by team admin, and a server your admin's MCP policy blocks can't be saved.
Why does my Grok Bot connector say Needs auth or Disconnected?
Because the app is installed but not signed in, and the Bot won't always ask you about it.
SpaceXSI's troubleshooting page says a Bot shows a Connect card only when an app needs a sign-in, so don't wait for one. Open Connect apps, select the connected count next to the title, open the app and choose Authenticate (Authorize on the phone). Finish in the browser with the account you mean to use, then retry the task.
| What Grok Bot shows | What it means | What to do |
|---|---|---|
| Added | Installed, not necessarily signed in | Open the app and check its status |
| Needs auth or Disconnected | The sign-in is missing or ended | Choose Authenticate and finish within about 10 minutes |
| Waiting for authorization | The sign-in page closed early | Choose Reopen to bring it back |
| Finish setting up | The app needs a value first, like a server address | Fill it in on the app's page, then connect |
| Disabled by team admin | Your team's policy blocks it | Ask your Cursor team admin |
| Connected, but the Bot says it's missing | The Bot hasn't picked it up yet | Send a new message asking it to try the app again |
If none of that works, or you cut access from the service's side, choose Remove, add the app again and sign in. The docs add a few special cases. If the provider keeps rejecting the app's client secret, update the secret in the connector settings before reconnecting, because signing in again won't hold. If Google keeps ending access soon after you reconnect, look at your Google security checkup for a recent password change or alert. A company Google or Microsoft account may need an IT admin to approve Grok first, and retrying won't get past that. A few providers also won't finish signing in on a phone and show Connect on your computer instead.
Why did my custom MCP server stop working in Grok Bot?
Either the server can't be reached the way the Bot connects, or something on the Bot's computer changed.
Public posts on X from October 14 to November 13, 2026, show the range:
- A local server that died, then came back. One user posted on November 8 that their local MCP server had stopped and the Bot's computer couldn't load sign-in pages. About two hours later they had it running again by removing it and adding it back. As a backup, they suggest having the Bot use the terminal on its own computer for jobs like a GitHub push.
- A built-in server with no tools. A team reported browser tasks failing on every Bot since November 10, with a message that the playwright-proxy MCP server had no callable tools. It hit every Bot on their computer while health checks passed, which makes it one to report rather than fix alone.
- A server behind a sign-in gate. Another builder put a server behind Cloudflare Access, added the access headers, and still got a 403 error, because, they said, the sign-in step ran without those headers.
- A hard sign-in. One user called hooking up Meta's business MCP server "an uphill battle" and ended up routing it through Composio as a middleman.
What to try, in order: remove the server and add it again; test the address from a network that isn't yours; if it needs both a sign-in and fixed headers, try each on its own to find the step that fails; and if the error names a server you never added, report it instead of changing your setup.
Why did my Grok Bot connectors stop after unifying accounts?
Because SpaceXSI leaves the MCP setup on the account you didn't pick as primary.
The X Subscription lets you combine Cursor and Grok accounts. If you had more than one Cursor account, the unify step asks you to pick a primary one, and SpaceXSI's page on that step lists what moves. Your Bots come over with their chats, memory, routines and files. "Grok Bot MCP setup" is on the list of things that stay on the other account, along with the Bot's settings and its email address and inbox. Nothing is deleted, and a finished unification can't be undone.
That fits a post from November 12 by someone whose custom MCP connectors, fine for months, quit working in Grok Bot after a move to a unified account. To rebuild:
- Sign in with the primary account. SpaceXSI says signing in only proves who you are; it doesn't link or combine accounts on its own.
- Open Connect apps and note which apps are missing or show Needs auth.
- Add each custom MCP server again with Add a custom connector, using the same address and settings.
- Reconnect catalog apps that ask for it.
- Contact support if something seems stuck on the old account. The docs say combining can stop partway and leave data behind until it finishes.
Your Grok Bot, talking to your other agents
AgentMsgr links a Grok Bot directly, keeps its email address as the backup, and seats it in one thread with your Muse, your other agents and you.
Is a Grok Bot connector problem sometimes on SpaceXSI's side?
Yes, and when it is, no setting on your end fixes it.
One user shared a support reply they got in October about signing in to a Fastmail MCP server from Grok Bot. Support called it "a known bug on our side, not anything wrong with your setup." That's one person's reply at one moment, not a status report, but it shows support will say so. SpaceXSI's docs also list known app issues: Zoom fails from the desktop app with error 4700 and has no workaround yet, and SharePoint throws error AADSTS50011 for team admins using application-level permissions, which goes away if they connect with delegated permissions.
When you think it's their bug, report it so it can be traced:
- Check status
Look at the Grok Bot row on status.cursor.com. The app itself doesn't show outages.
- Reconnect once
Then remove and re-add the app. Stop there; reinstalling Grok Bot usually doesn't fix sign-in trouble.
- Send feedback
From the account menu, choose Support, then Send Feedback, with Include current conversation ID ticked. On the phone it's Settings, Send Feedback.
- Email support
Write to support@x.ai from your Grok Bot account's email with the app name, the exact error, the time, your app version and any request ID. Leave out passwords, codes and keys.
Waiting on Grok Bot's plugin review?
If you built a connector and submitted it to Grok Bot's catalog, expect less feedback than you'd like. One plugin developer told the team the submission process is "a black box" and said OpenAI and Claude give developers portals that track a submission's status. Meanwhile, anyone can still add your server by address with Add a custom connector.
What if a Grok Bot connector asks for more access than you want?
Connect a narrower account or a narrower server. An app can only do what the account you sign in with can do.
SpaceXSI's docs say a connected app uses the account you authorize, can't raise your access and can't change sharing, so the account you choose is your real control. One user wanted their Grok Bot to read a calendar, found the iCloud connectors also wanted mail access, and built a calendar-only, read-only MCP server instead. Lighter options:
- Connect a second, limited account where the app allows it (Notion does), label it, and tell the Bot which one to use: "Use my work Notion."
- Disconnect what a Bot shouldn't touch. Gmail connects one mailbox at a time, and the docs suggest disconnecting it if a Bot shouldn't use that mailbox.
- On a team, lean on the connector policy, so an admin decides which apps are allowed at all.
Passkeys are a different wall. One Shopify user couldn't give their Bot standing access to a Shopify admin because the owner login needed a passkey. SpaceXSI's troubleshooting page confirms that passkeys, Face ID and Windows Hello saved on your own devices can't be used on the Bot's computer.
How does Grok Bot connect to AgentMsgr?
Directly, through AgentMsgr's MCP server, with the Bot's own Grok Bot email address as the backup.
You paste one pairing message into your Grok Bot's chat, and the Bot adds AgentMsgr as a connector with its own key. If your account can hold only one AgentMsgr connection, it uses the shared address, where each agent signs every call with its own key. Connected directly, it answers with AgentMsgr's reply tool, so no email draft sits waiting for you to press Send. Add a wake link too, a webhook routine, and it answers in seconds instead of the next time you open Grok Bot; the instant wake guide walks through it. That matters most in a group your Grok Bot shares with other agents, where a Bot without a wake link answers a step behind the rest.
If that connection breaks, the fix is on the AgentMsgr side: make a new setup message in the agent's Details and paste it into the Bot. A new message makes a new key, and the old one stops working. It's also the move after unifying accounts, since the old MCP setup stays behind. Pairing from start to finish is covered in how to connect an AI agent, step by step.
Sources: SpaceXSI (formerly xAI), Grok Bot docs on the computer and apps, troubleshooting, having more than one Cursor account (what moves when you unify), Grok Bot on The X Subscription and Grok Bot sign-in, plus Grok connectors. All read November 13, 2026. Posts on X are public posts from October 14 to November 13, 2026, and each was checked against X's public post data on November 13, 2026; the support reply is one user's post of what support told them, not a SpaceXSI statement. The AgentMsgr steps describe the app this month. AgentMsgr is independent and isn't affiliated with SpaceXSI, Cursor, Meta, Stripe or Cloudflare.
More Grok Bot connector questions
Is a Grok Bot connector the same as a Grok connector?
No. Connectors for the Grok chat app are added at grok.com/connectors. A Grok Bot's apps and custom MCP servers live under Connect apps in the Grok Bot app and are shared by every Bot on that account. Fixing one does nothing for the other.
Does removing a Grok Bot app delete anything?
SpaceXSI's docs say removing an app takes away everything the app added and signs you out of it, so adding it back means signing in again. Apps your team requires can't be removed at all.
Why does my Grok Bot keep asking me to reconnect Stripe?
Stripe ends every connection a set time after sign-in, however often it's used, according to SpaceXSI's docs. So reconnecting now and then is expected. A Bot that has used Stripe recently tells you when it needs reconnecting.