The short answer

Plugins, also called connectors, let a Bot use services like Gmail, Slack, Notion or Linear through a structured connection instead of clicking through a website. Install one from Connect Apps (formerly Marketplace) in the sidebar, finish the sign-in in your browser, and every Bot on your account can use it. A custom MCP server can be added by URL or, according to the docs read November 12, by a command that runs on the Bot's computer.

This page follows the official docs, Cursor's help pages and the changelog through 0.75.5 (October 23), checked October 25, 2026, plus Cursor staff replies on the forum, which we attribute and have not reproduced. We have not tested any connector.

Documentation: Computer and apps: connect an app ↗ Grok Bot security ↗ Cursor help: connect plugins ↗ Cursor help: give your Bot an email address ↗ Forum: custom connectors (staff reply, August 30) ↗

RouteUse it whenKeep in mind
A plugin from Connect AppsThe service is in the catalogAccount-wide; tokens stay on Cursor's backend; Added is not the same as signed in
A custom remote MCP serverYou run or trust an HTTPS MCP endpointMust be publicly reachable; OAuth only, no secret headers; redirect issues are open
A command (stdio) MCP server on the Bot's computerA server ships as a package you can run with npx or uvxRuns on the cloud computer, not your laptop; keep credentials out of its command and arguments
The Bot's browserThere is no plugin, or the work is visualUses your signed-in session on the shared computer; see our connectors or browser guide
A secret for a scriptAn API has no plugin sign-inUse a secure secret request; never paste a key into chat
The Email pluginA Bot needs its own inbox, for sign-ups, receipts or mail-triggered routinesGives your Bots a new mail.grokbot.com address rather than connecting one you have; one per account, permanent

Plugins, connectors, Marketplace, Connect Apps: the names

The docs use connector and plugin for the same thing: connectors are installed as plugins. Where you install them has moved. The changelog shows the sidebar's Marketplace button became Connect apps in 0.60.0 (September 26), Marketplace stopped listing Bots and searched only plugins in 0.63.0 (September 29), and Marketplace became Connect Apps, with category chips and Recommended for you first, in 0.67.0 (October 2). Bot templates moved to the web; see our Marketplace and templates guide.

The documentation is catching up. By October 11, Cursor's help pages and the docs.x.ai page on connecting apps (updated October 9) said Connect apps, while the docs.x.ai settings and skills pages still said Marketplace. A Cursor staff member's October 5 directions cover both: Marketplace (or Connect apps) at the bottom of the sidebar, or Cmd+Shift+M; the docs' shortcut list also gives Cmd/Ctrl+Shift+W. Since 0.75.2, Connect Apps shows each plugin's own logo and waits longer for your plugins instead of showing Couldn't refresh, and built-in plugins no longer offer an Uninstall that failed.

GitHub is a special case; staff said on September 28 that it is now built into Grok Bot through your connected Cursor GitHub account, replacing the old marketplace plugin. The October releases extended it. Since 0.71.2, when GitHub cannot see a repository the Bot stops retrying and links the GitHub page where you grant access, and when GitHub is not connected it offers a single Connect GitHub action. Since 0.75.2 the GitHub connector can list your repositories, compare commits, list a pull request's commits and read branch and issue comments, and pull requests, issues and repositories mentioned in replies are links.

Documentation: Grok Bot changelog (Marketplace to Connect Apps, 0.60 to 0.67; connector changes in 0.69 to 0.70.2) ↗ Grok Bot changelog: 0.71.2 (200 plugin skills, two-minute connector calls, October 14) ↗ Grok Bot changelog: 0.75.2 (Zoho CRM, GitHub, own OAuth client callback URLs, October 22) ↗ Computer and apps: connect an app ↗ Settings: plugins and skills ↗ Message and collaborate: keyboard shortcuts ↗ Cursor help: connect plugins ↗ Forum: delisted GitHub plugin, GitHub now built in (staff reply, September 28) ↗

Install and authorize a plugin

These steps combine the official docs and Cursor's help. On mobile, Cursor's help says to tap your avatar at the top left and choose Connect apps.

Documentation: Computer and apps: connect an app ↗ Settings: plugins and skills ↗ Cursor help: connect plugins ↗ Cursor help: how-tos (reconnect a plugin, second accounts) ↗ Grok Bot changelog (Marketplace to Connect Apps, 0.60 to 0.67; connector changes in 0.69 to 0.70.2) ↗ Grok Bot changelog: 0.75.2 (Zoho CRM, GitHub, own OAuth client callback URLs, October 22) ↗ Grok Bot changelog: 0.75.5 (plugins with several servers, October 23) ↗

  1. Open Connect Apps in the sidebar, or follow a Connect card in chat.
  2. Find the plugin and add it. Since 0.63.0, a plugin that needs a sign-in, such as Gmail, starts that sign-in right away. Since 0.75.8 (October 24), a plugin a Bot installs while it is working is usable in that same task: the Bot can use the plugin's skills right away.
  3. Finish the provider's sign-in in your browser within about 10 minutes. If sign-in does not finish, choose Reconnect on the plugin, or Reopen on the in-chat card, to bring the sign-in page back; if the card says it failed, choose Retry.
  4. Confirm the plugin appears under Installed and is authorized. Added only means installed; choose Authenticate (Authorize on the phone) if it shows Needs auth or Disconnected.
  5. In chat, type @ to attach the connector to a task. To review or switch off individual tools, open Your plugins → Manage plugins and skills.
  • Shortcut: the October 11 changelog entry (0.69.0 to 0.70.2) says giving a Bot a connector link installs the matching catalog plugin when there is one, and plugins installed from chat or the web are ready on the Bot's computer.
  • Glean asks for your Glean MCP URL when you add it, then connects after you sign in to Glean in the browser; ask your Glean admin for the URL first.
  • QuickBooks Online is now available to connect, according to the same entry.
  • Connectors that come with an app, such as Figma, Notion and Canva, can show it as an interactive card in the chat.
  • Since 0.75.2 (October 22), naming a service makes the Bot show that connector's connect card in its first reply, and a connector that signs you out or rejects a sign-in says why, such as a restricted Google account, and how to fix it.
  • Setting up a plugin with your own OAuth client now lists the callback URLs to register (0.75.2); register exactly those with the provider before you sign in.
  • Zoho CRM can be connected, and you choose your account's regional data center before you sign in (0.75.2).
  • Plugins with several servers, such as Salesforce, show each server as its own row since 0.75.5 (October 23), so sign in to every row, not just the first.
  • Since 0.75.5, when the Bot hands you its computer to sign in to a site that has a connector, it also offers that connector's connect card. The docs say a connector's token stays on Cursor's backend, while a browser sign-in lives on the shared computer.

Where tokens live, and who can use a plugin

The docs say OAuth tokens stay on Cursor's connector backend, Bots invoke tools without receiving them, and tokens are never stored on the Bot's computer. That makes a plugin sturdier than a browser login, which depends on cookies on the shared computer. A plugin can do only what the connected account can already do; it cannot raise your access or change sharing. The Slack plugin, for example, posts as the Slack user you connected and only where that user can post.

Installed plugins are account-wide: every Bot on your account can use every connected account. Cursor's help says some plugins, such as Notion, can add a second account, while Gmail connects one mailbox at a time. On a Cursor team, the team's connector policy decides which plugins members can use, a blocked one shows Disabled by team admin, and the MCP allowlist is Enterprise only. Blocking a plugin does not block that service's website. Shared Bots treat plugins differently again; see our Shared Bots guide.

Some reading needs no plugin at all. The docs say Bots can search and read what is public on X without connecting an account; add the X plugin only for your DMs, bookmarks, home timeline or who liked your posts. One exception to removing a plugin: since 0.75.5, asking a Bot about your X account connects X through your linked X account even if you removed the X plugin, and connecting X also connects X Money.

Plugin skills have a higher ceiling: since 0.71.2 (October 14) a Bot can use up to 200 skills from your installed plugins instead of 24. And since 0.75.2, turning a Bot's tool on or off applies the state you saw, so an outdated list cannot turn a blocked tool back on.

Documentation: Teams and enterprises: connector policy ↗ Grok Bot security ↗ Computer and apps: connect an app ↗ Cursor help: connect plugins ↗ Cursor help: how-tos (reconnect a plugin, second accounts) ↗ Grok Bot changelog: 0.71.2 (200 plugin skills, two-minute connector calls, October 14) ↗ Grok Bot changelog: 0.75.2 (Zoho CRM, GitHub, own OAuth client callback URLs, October 22) ↗ Grok Bot changelog: 0.75.5 (plugins with several servers, October 23) ↗

Add a custom MCP server

There are now two ways. docs.x.ai's computer and apps page, read November 12, says that in the desktop app you can choose Add a custom connector at the bottom of Connect apps, enter a Name and pick a Type: Remote HTTPS takes a Server URL, with optional HTTP headers and an OAuth Client ID, and Command takes a Command and its Arguments; Add plugin saves it, and a server your team admin's MCP policy blocks cannot be saved. The same page says a Bot can add an MCP server by URL or by a command that runs on its computer, and that adding a server on a private network, or one that uses a private certificate authority, asks for your approval first. The staff answers below predate that page. A Cursor staff member said on August 30 that you tell the Bot in chat to add the MCP server, and that it must be a public HTTPS URL using streamable HTTP or SSE. OAuth discovery runs from Cursor's infrastructure, so another staff answer on August 12 said the endpoint must be reachable over HTTPS from the open internet; a server behind your VPN or on localhost will not work. Staff also said on September 17 that connectors authenticate only through OAuth, with no safe way to enter a secret header.

Servers on your own laptop are not attached. Staff said on August 13 that Grok Bot does not attach MCP servers that run on your own machine, whether over stdio or on localhost. A command-style server can instead run on the Bot's cloud computer: a staff reply on September 8 suggested registering servers as npx or uvx commands or keeping wrapper scripts on the computer, and on September 28 staff explained re-pointing a custom stdio server by adding it again under the same name. The Shared Bots docs warn that teammates can read a command server's command and arguments, so never put a credential in either.

Documentation: Forum: custom connectors (staff reply, August 30) ↗ Forum: custom remote MCP OAuth never starts (staff answer, August 12) ↗ Forum: custom MCP OAuth fails with redirect_uri not allowed (staff replies, September 16 to 25) ↗ Forum: does Grok Bot support local MCP? (staff reply, August 13) ↗ Forum: stdio MCP server paths on the Bot's computer (staff reply, September 8) ↗ Forum: edit a custom stdio MCP server in place (staff reply, September 28) ↗ Team Bots (called Shared Bots in late October 2026): plugin types ↗

Try this brief

Add a custom MCP server named [name] at [https URL] using [streamable HTTP or SSE]. Do not paste any key or token into this chat; if the server needs one, start its OAuth sign-in or ask me for a secure secret. When it is connected, list the tools it exposes and run one read-only call on [harmless test input]. Do not call any tool that creates, changes or deletes data.

Original editorial template. Replace placeholders and review access before running.

Known issues as of October 28

These are the open or recently fixed plugin problems with a Cursor staff reply or a help-page entry. On October 25 we rechecked the custom MCP OAuth, MCP-Protocol-Version, outbound-traffic and Vercel threads and Cursor's help page; the other forum rows are as of October 11. None of the changelog entries through 0.78.1 (October 27) name the open issues below as fixed, although 0.77.0 says a custom MCP server that uses a private certificate authority now works once you approve that authority, and that a connector whose server refuses registration shows Error instead of a sign-in that cannot work.

Documentation: Grok Bot changelog: 0.78.4 (Tailscale MCP message, team plugin allowlist, November 3) ↗ Grok Bot changelog: 0.79.2 (connector search order, Gopuff, blocked connector reason, November 5) ↗ Grok Bot changelog: 0.79.3 (1Password disconnect fix, November 6) ↗ Grok Bot changelog: 0.78.1 (connector names instead of IDs, Still signing in?, Slack disconnect, October 27) ↗ Forum: custom MCP OAuth fails with redirect_uri not allowed (staff replies, September 16 to 25) ↗ Forum: IBKR MCP OAuth fails in Grok Bot (staff replies August 12 and September 14, user reports to November 1) ↗ Cursor help: connect plugins ↗ Forum: Zoom plugin OAuth error 4700 (staff replies) ↗ Forum: Vercel plugin OAuth redirect URL invalid (staff reply, September 21) ↗ Forum: MCP shows connected but the Bot gets MCP server not found (staff fix, September 28) ↗ Forum: delisted GitHub plugin, GitHub now built in (staff reply, September 28) ↗ Grok Bot changelog (Marketplace to Connect Apps, 0.60 to 0.67; connector changes in 0.69 to 0.70.2) ↗ Grok Bot changelog: 0.71.2 (200 plugin skills, two-minute connector calls, October 14) ↗ Grok Bot changelog: 0.75.5 (plugins with several servers, October 23) ↗ Grok Bot changelog: 0.77.0 (Connect and Reconnect states, private CA for custom MCP, hour-long sign-ins, October 26) ↗ Forum: remote MCP requests omit MCP-Protocol-Version on reused sessions (staff reply, October 8) ↗ Forum: outbound connections other than HTTPS blocked on the Bot's computer (staff reply, October 2) ↗

SymptomWhat Cursor saidStatus
A connector sign-in started from a connect card fails if you take more than a few minutes, or a connect card appears for an error that is not a sign-in0.77.0 (October 26): connector sign-ins can finish up to an hour after you start them; connect cards appear only when a connector says you need to sign in, keep waiting while your newest sign-in page is open, and a refused sign-in sends you back with the reasonFixed (October 26)
Google apps ask you to reconnect when Google is only throttling requests, or a Google account without Gmail keeps disconnecting0.77.0: Google apps stay connected and the Bot says to try again later; an account without Gmail stays connected and the Bot asks for one that has GmailFixed (October 26)
Connector buttons read differently in different places, so it is unclear whether a plugin is signed in0.77.0: buttons say Connect everywhere, a signed-out connector shows Not connected, Your plugins offers Reconnect for one that stopped working, and plugins show Connecting… then Connected during sign-inChanged (October 26)
Background work keeps calling a connector that signed you out0.77.0: it stops and tells you to reconnect the connector; when background work needs one of your apps, the Bot asks with an allow card in the app, or Allow once and Skip in SlackFixed (October 26)
App cards, plugin rows and connector errors show an internal ID instead of the app's name0.78.1 (October 27): they show the connector's name; when a connector needs a permission its connection cannot request, the Bot says reconnecting will not help; when a plugin is not available, the Bot says so instead of listing the whole catalogFixed (October 27)
A connect card says the sign-in did not finish while you are still signing in, or signing in to a Google account that is already connected produces several reconnect cards0.78.1: after 10 minutes the card asks Still signing in?; a Google account that is already connected is reused, with one reconnect card; Google Calendar asks you to reconnect only when signing in again can grant the missing permission; connector tools stay listed while a tool list reloadsFixed (October 27)
Remove from Slack leaves Slack connected, or a Slack connect link opened while signed in to another account keeps failing0.78.1: Remove from Slack disconnects Slack; the link works once you sign in as the right account and connect againFixed (October 27)
The Tailscale plugin installs on an account that cannot use it0.78.1: it shows Not available yet on those accountsChanged (October 27)
An MCP server on a private Tailscale network fails without saying what to do0.78.4 (November 3): the message says to connect your tailnet from the Tailscale plugin, then try againChanged (November 3)
GitHub shows Disabled by team admin when no team rule blocks it, or a blocked plugin or custom connector gives no reason0.78.4: GitHub shows the label only when your team's MCP rules actually block it, plugin installs follow your team's allowlist, and a blocked plugin says Your team admin has disabled this plugin's MCP servers; 0.79.2 (November 5): a custom connector your team policy blocks shows the admin's reason instead of Something went wrongFixed (November 3 and 5)
Disconnecting 1Password shows a Service Unavailable message or leaves the plugin page on Connected0.79.3 (November 6): it no longer does; 0.79.2 also made a 1Password connection that does not finish ask you to try connecting againFixed (November 6)
Typing part of a connector's name does not bring it to the top of search0.79.2: connector search lists name matches first, so typing salesf shows Salesforce at the topChanged (November 5)
Custom MCP OAuth fails before sign-in: redirect_uri not allowed (for example behind Cloudflare Access)Registration sends a cursor:// callback that https-only providers reject. For Cloudflare Access, staff confirmed on October 19 that adding cursor://anysphere.cursor-mcp/oauth/callback to the application's allowed redirect URIs through the Access Applications API works. Providers that accept only https or loopback callbacks, such as Home Assistant, still fail, and on October 21 staff traced a separate Home Assistant failure to an oversized header on Cursor's client metadata document, with no workaround yetWorkaround for Cloudflare Access; open for other providers (October 21)
Interactive Brokers (IBKR) MCP: Failed to load MCP server and sign-in never startsAdding IBKR's public MCP address (https://api.ibkr.com/v1/api/mcp-public) as a custom server failed OAuth with a redirect_uris error, though the same connector works on grok.com. Cursor staff (mohitjain) said on August 12 and September 14 that the fault is on Cursor's side, tracked with no timeline, and offered an mcp-remote bridge in the Cursor IDE as the only workaround. IBKR is not listed under Connect Apps; on November 1 one user said adding the address by hand now works for them, while another still could not connect (user reports, not confirmed by staff)Open; user report of it working (November 1)
A custom remote MCP server connects and lists tools, then later calls fail with an empty HTTP 400When Grok Bot reuses an MCP session it leaves out the MCP-Protocol-Version header, which strict servers reject; staff confirmed it and flagged a fix. Reconnecting does not help; a server that accepts requests without the header worksOpen (October 8)
A command (stdio) MCP server or script on the Bot's computer cannot reach a database, mail, SSH or other non-HTTPS portSince about October 1 some Bot computers allow outbound connections only over HTTPS on port 443; staff said on October 2 it is not intended, is tracked and needs no reset; HTTPS endpoints and cloning over HTTPS still workOpen; users still reporting it October 22
Zoom authorization fails with error 4700 (Invalid redirect)Cursor's help calls it a known issue with no workaroundOpen (help page, October 25)
SharePoint admin consent fails with AADSTS50011 (redirect URI mismatch) on Application-level permissionsCursor's help calls it a known issue; the workaround is to connect with Delegated permissions from the dashboard's Integrations pageOpen, with workaround (help page, October 25)
A connector's new tools or fields, for example on X, are missing until you reconnect it0.75.8 (October 24): Bots can use them without you reconnecting itFixed (October 24)
A connector whose sign-in expired still shows Connected in the app while the Bot says it is signed out0.75.8 (October 24), on Grok Bot 0.71.2 or later: the app shows Authenticate instead, matching what the Bot saysFixed (October 24)
Images a connector returns as files come through garbled, as do other binary files0.75.8 (October 24): images reach the Bot as images and other binary files are no longer read as textFixed (October 24)
Connector calls time out after one minute0.71.2 (October 14): calls now wait up to two minutes, longer while the connector reports progressFixed (October 14)
A plugin with several servers, such as Salesforce, shows only one, so you cannot sign in to the rest0.75.5 (October 23): each server shows as its own rowFixed (October 23)
Vercel plugin: redirect URL is invalidBroken since about September 16; staff said the team had identified the causeNo fix confirmed in the thread (September 21)
Plugin shows connected but the Bot reports MCP server not foundA server-side change left background tasks without connectors; a fix rolled outFixed (September 28)
An old GitHub plugin cannot be removed and shows 0 toolsGitHub is now built in through your Cursor GitHub account; staff removed leftovers on requestWorkaround (September 28 to October 7)
A rate-limited connector makes the Bot loop, or calls fail on a Notion link or Slack channel nameChangelog entry of October 11 (0.69.0 to 0.70.2): Bots now wait for the retry delay, and connector calls fail less often, including fixes for wrongly shaped arguments, Notion links and Slack channel namesFixed (October 11)
A Bot signs you out of a connector while repairing itSame entry: Bots no longer do this, and a connector account you signed out of stays signed outFixed (October 11)
Connecting fails because another app is using the sign-in portChangelog 0.67.0: connecting an app now finishes anyway, and a failed sign-in page explains whyFixed (October 2)

Plugins in templates and Shared Bots

A shared Bot template lists its first-party plugins, but each new owner reinstalls and authenticates them; xAI's template guide says templates do not carry MCP servers, custom code or scripts. On a Shared Bot, a plugin that signs in with an account uses the account of whoever is talking to the Bot, while a plugin configured with a key uses the Bot's own credential for everyone, and a custom Remote HTTPS server can use either. Since 0.71.2, plugins on a Shared Bot use team admin settings, such as the Datadog site, and since 0.75.5 Shared Bots name connectors as your plugin list does when they ask to use one or say whose they used. Since 0.77.0 (October 26), plugins a team admin would not allow show Disabled by team admin, and linked teammates on a Shared Bot use their own connectors and memory; the docs now call Team Bots Shared Bots. For Gmail and Google Workspace specifics, see our Gmail guide; for the security model, see Is Grok Bot safe?.

Documentation: xAI: Templates for Grok Bot (September 8, 2026) ↗ Team Bots (called Shared Bots in late October 2026): plugin types ↗ Grok Bot changelog: 0.71.2 (200 plugin skills, two-minute connector calls, October 14) ↗ Grok Bot changelog: 0.75.5 (plugins with several servers, October 23) ↗ Grok Bot changelog: 0.77.0 (Connect and Reconnect states, private CA for custom MCP, hour-long sign-ins, October 26) ↗

Quick answers

Where did Marketplace go in Grok Bot?

It was renamed. The changelog shows the sidebar button became Connect apps in 0.60.0 (September 26), Marketplace stopped showing Bots and focused on plugins in 0.63.0 (September 29), and Marketplace became Connect Apps in 0.67.0 (October 2). Bot templates moved to the web Marketplace at x.ai/bot/marketplace. A Cursor staff member wrote on October 5: open Marketplace (or Connect apps) at the bottom of the sidebar, or press Cmd+Shift+M; the docs also list Cmd/Ctrl+Shift+W.

Can Grok Bot use an MCP server running on my laptop?

No. A Cursor staff member said on August 13 that Grok Bot does not attach MCP servers that run on your own machine, whether over stdio or listening on localhost, because Bots work on a cloud computer. Use a public HTTPS server, a catalog plugin, or the Bot's browser. Staff have since described running stdio servers on the Bot's own cloud computer instead.

Does the Bot see my OAuth tokens?

No, according to the docs. OAuth tokens stay on Cursor's connector backend, Bots invoke tools without receiving them, and tokens are never stored on the Bot's computer. A plugin can do only what the connected account can already do in that service.

Can I connect two accounts for the same service?

For some plugins. Cursor's help says Notion and some others can add a second account with Add Another Account, and the 0.77.0 changelog (October 26) says adding a second Gmail or Google Drive account now opens Google's account picker, and removing one account leaves the others in place. Every Bot on your account can use every connected account, so disconnect one a Bot should not use.

Do Bot templates include plugins and MCP servers?

Plugins are listed, but each new owner reinstalls and authenticates them. xAI's September 8 template guide says templates do not carry MCP servers, custom code or scripts, and suggests having the Bot write setup instructions into the template for complex setups.

Bots for this job

Directory listings that match this guide, read from each creator's public share page. They are not tested picks: check what a Bot can reach before you add it.

Browse: Bots for mcp · Bots that work with GitHub

  • Tinkabot by lauren 🎀: Turns an API into a plugin your other bots can just pick up and use
  • GitHub Steward by Lee Talley: GitHub Steward runs GitHub for you from chat: it sets up one board of your work, keeps your folders private, makes changes as drafts, and asks before
  • Compute Spread by Sam E: Cuts AI spend by preferring connectors and public data, one lean batch, and the smallest tool that still works

Sources & next steps

Capabilities are grounded in the documentation below. The workflow design and acceptance checks are editorial suggestions.

Build your own workflow brief →