METAGROK
GROK BOT / connect-a-plugin-to-grok-bot

Grok Bot

Connect a plugin to Grok Bot

connect-a-plugin-to-grok-bot

Plugins give Bots a structured way to work with services like Gmail, Notion, and Slack. Prefer a plugin over clicking through a website when one exists. Official guide: Work with Grok Bot → Connect plugins, and Settings and notifications → Plugins.

Connect from the app

  1. Open Plugins in the sidebar, or follow an in-chat Connect card.
  2. Choose the service from Marketplace, or open Yours for installed plugins and private skills.
  3. Finish the provider login in your browser.
  4. Confirm the plugin shows as connected for your account.
  5. Under Yours, enable or disable individual plugin tools if you need a narrower tool set for this Bot.

An installed plugin may still need browser authentication the first time a Bot uses it. On Teams and Enterprise plans, team-provided plugins may be required or restricted by an admin.

How plugins behave on your account

  • Plugins are account-wide. An installed plugin is available to every Bot you run.
  • Plugin logins stay off the computer. OAuth tokens are held on Cursor's connector backend, and the Bot invokes tools without receiving those tokens.
  • Team policy applies. A plugin blocked by your team's connector policy shows Disabled by team admin. Blocking a plugin does not block that service's website. Closing that second path takes Network Controls, which is Enterprise only.

When a plugin is missing or blocked

If Marketplace does not list the service you need, use the computer browser for that site and keep consequential actions behind approval. If the plugin shows Disabled by team admin, ask your admin whether the connector is allowed; do not work around a blocked plugin with a stolen session or pasted credentials.

Pitfalls

  • Treating a plugin login as Bot-specific — it is account-wide for every Bot you run.
  • Pasting OAuth tokens or API keys into chat when a plugin Connect flow exists.
  • Assuming a blocked plugin also blocks the website — it does not, unless Network Controls close that path.
  • Leaving every plugin tool enabled when the Bot only needs a read-only subset.