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 approval-first 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
A Bot's first local action asks the member for consent, and the approval card shows the exact command — so you can watch the Busabase setup step before it runs. Access comes with SuperGrok Heavy, Cursor Ultra, or a one-time trial; teams and enterprises go through Cursor.
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 VM — xAI's 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 exposes custom MCP servers as connectors:
- Go to grok.com/connectors.
- Click New Connector, then choose Custom.
- Enter the Busabase MCP server URL and complete the authentication it asks for.
Grok discovers the tools your MCP server exposes and makes them available in conversations, the same as its built-in connectors.
The server has to be reachable from the public internet. Busabase Cloud already is. For Busabase Personal Desktop on localhost:15419, expose it first — Busabase has a built-in Tunnel, and xAI's docs also describe using a tunnelling service such as ngrok.
Grok Bot documentation · Grok connectors documentation
Known gotchas
A custom connector's MCP server must be reachable from the public internet — Busabase Cloud is, but Busabase Personal Desktop on localhost needs Busabase's Tunnel or a service like ngrok first. xAI's docs say to "complete any required authentication" without listing which auth methods the custom-connector dialog supports, so the exact flow against Busabase's OAuth is not documented on their side.
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, reviewed access, and every change it makes afterwards arrives as a proposal you approve.
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.