Busabase for Grok BotConnect Grok Bot to Busabase
Always-on AI teammates from xAI; each Bot gets a persistent cloud VM with a browser, filesystem, and terminal.
Paste this into Grok Bot
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.
Busabase
Give your agent this one instruction
You end up with more than a connector: the busabase skill carries the whole change-request workflow, the CLI, and the full API — available in every future session without re-pasting anything.
Asks first
Busabase Cloud or Personal Desktop — your call, before anything happens.
Connects
Signs you in and stores the credential itself. No API key to copy by hand.
Seeds a Base
Creates and fills your first Base, so the workspace is not an empty screen.
Installs the skills
busabase and busabase-app-creator become permanent, for every session after this.
For this agent
Grok Bot 'skills' are its own saved instructions (a skill is a reusable set of instructions, referenced with `/`), not documented as the SKILL.md Agent Skills format, so skill-docs-url stays null. The Skill flow installs Busabase skills with `npx skills add` onto the Bot's shared cloud computer.
Prefer a connector?
If you would rather wire Busabase in as MCP tools than let the agent install a skill, use the server URL below.
At a glance
- Vendor
- xAI
- How it connects
- Plugin / Skill · MCP + OAuth
- Transport
- Unknown
- Authentication
- Unknown
Each Bot runs on its own persistent cloud computer: the Grok Bot docs state it has "a browser, filesystem, and terminal", so the Skill path applies. Hand the Bot the prompt above and it connects itself.
Prefer a connector instead?
Grok Bot connectors are installed as plugins from Connect apps in the sidebar (Browse, Add, finish authentication in the browser, then @ the connector in chat). the Grok Bot docs list "Custom MCP server, Remote HTTPS" (and OAuth sign-in) as a plugin type for Team Bots, but do not publish a step-by-step for adding a custom MCP server to a personal Bot, so this row does not give connector steps for Grok Bot.
The separate Grok chat app does document it: go to grok.com/connectors, click New Connector, choose Custom, enter https://busabase.com/api/mcp, and complete authentication. That is Grok chat, not Grok Bot, and the server must be reachable from the public internet.
Grok Bot documentation · Use the computer and apps · Grok connectors documentation
Known gotchas
The grok.com/connectors custom-connector flow is documented for Grok chat; for Grok Bot, the Grok Bot docs describe plugins via Connect apps and mention a custom MCP server (Remote HTTPS, OAuth sign-in supported) only for Team Bots, with no add-steps for a personal Bot. Any custom MCP server must be reachable from the public internet (Busabase Cloud is; Busabase Desktop on localhost needs Busabase's Tunnel or ngrok). All your Bots share one cloud computer, browser sessions and files, so a login or key given to one Bot is available to the others. Grok Bot requires an eligible plan (paid Cursor plan, The X Subscription Premium/Super/Ultra, or linked SuperGrok) and uses Cursor sign-in.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | Grok Bot |  Claude Code |  Cursor |
|---|---|---|---|
| Type | Agent platforms | Terminal agents | AI editors |
| Recommended path | Agent Skill | Agent Skill | Agent Skill |
| How it connects | Plugin / Skill · MCP + OAuth | MCP + OAuth · Plugin / Skill | MCP + OAuth · Plugin / Skill |
| Transport | Unknown | Streamable HTTP | Streamable HTTP |
| Authentication | Unknown | OAuth (dynamic registration) | OAuth (dynamic registration) |
Written from this agent's own documentation. We have not re-run every step on a real machine, so check the linked docs if a command has changed.
Let your agent do the setup
One instruction, one authorization, and every change it makes afterwards carries a message and a diff you can check or revert.
Browse every agentPaste this into Grok Bot
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.