Grok Bot Plugins & Connectors
A Bot can reach a service in two ways: a connector (a plugin from the Marketplace, authorised once) or computer use (it drives the browser like you would). Connectors are faster and more reliable, and they keep your credentials off the computer. Use computer use for everything that has no connector.
Connector vs computer use
| Connector (plugin) | Computer use (browser) | |
|---|---|---|
| Setup | Marketplace → add account → authorize | Log in once with computer takeover |
| Credentials | Tokens stay on Cursor's backend and are never stored on the computer | A browser session on the shared computer, reusable by every Bot |
| Reliability | High | Sites may block automation, expire sessions, or show a CAPTCHA |
| Concurrency | Many Bots at once | One computer-use task per Bot at a time |
Adding a connector
- Open Marketplace in the sidebar and search for the service (Gmail, Outlook, ClickUp and so on).
- Add account → name it → Authorize → approve in the browser.
- Label each account when you connect several ("Nate – main", "Support"), so you can assign one inbox per Bot and refer to it by name in instructions.
Mention a connector in chat with @ to point a Bot at it explicitly.
Give Bots their own email instead of yours
The most useful pattern we've seen (1, 2): rather than logging a Bot into your accounts, give it its own address from an agent-inbox service such as AgentMail (which has a native connector), and invite that address to the tools it needs. You get a clean audit trail, easy revocation, and no Bot able to read your personal mail. Add a webhook routine and the Bot wakes whenever mail arrives.
- Create an inbox in AgentMail (the free tier covers a few). It uses the
agentmail.todomain unless you add a custom one. - In Grok Bot: Marketplace → AgentMail → Add account → Authorize.
- Tell the Bot which AgentMail account is its own, and that it should only act on mail to that inbox.
MCP and third-party tool hubs
Grok Bot's action logs record connector calls as MCP tool calls, and creators have wired in tool hubs such as Composio and MCP voice services (techniques, briefing podcast). Each hub you add is another party holding tokens for your accounts. Add them one at a time, and only for jobs a native connector can't do.
On a team plan
Grok Bot inherits your team's Cursor connector policy. There is no separate Grok Bot allowlist. A connector your admin has blocked shows as "Disabled by team admin". See teams.
Hub · Setup · Skills & routines · Plugins · Pricing · Security · Teams · vs OpenClaw & Hermes · FAQ · Grok Bot news
Sources: xAI's Grok Bot documentation (docs.x.ai) and Cursor's Grok Bot plans page, checked 2026-09-19. Grok Bot is in beta and changes weekly. Where the docs and a video disagree, we follow the docs and say so.