Busabase for Grok Build

Connect Grok Build to Busabase

xAI's terminal coding agent (the `grok` command): an interactive fullscreen TUI with plan mode, parallel subagents in their own worktrees, headless mode (`grok -p`) for scripts, and ACP support for embedding in other apps. Launched in early beta on 2026-05-25 for SuperGrok and X Premium+ subscribers; it picks up a repo's AGENTS.md, plugins, hooks, skills and MCP servers out of the box and is fully compatible with Claude Code configuration with zero setup.

Paste this into Grok Build

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.

Read the Grok Build Skills documentation
Busabase
Agent Skill
A Base of posts in a Busabase workspace, with records, views, and agent prompts

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

Skills are SKILL.md folders (YAML frontmatter; extra keys ignored) discovered in `./.grok/skills/` up to the repo root, `~/.grok/skills/`, `~/.agents/skills/`, enabled plugins' `skills/` directories and extra `[skills] paths` in `~/.grok/config.toml`. User-invocable skills also appear as `/ <skill-name>` slash commands. Grok also reads Claude Code marketplaces, plugins, skills and instruction files with no extra setup.

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
MCP + OAuth · Plugin / Skill
Transport
Streamable HTTP
Authentication
Unknown
Config file
~/.grok/config.toml (project: .grok/config.toml)
Run this
grok mcp add --transport http busabase https://busabase.com/api/mcp
grok mcp list

Grok Build runs in your terminal and can execute shell commands and fetch URLs, so the Skill path applies. Install it (curl -fsSL https://x.ai/cli/install.sh | bash), start grok in your project, and ask: Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Grok discovers SKILL.md skills in ./.grok/skills/, ~/.grok/skills/ and ~/.agents/skills/, so the permanent Busabase skills the setup installs are picked up on later sessions.

Prefer a connector?

Add Busabase as a remote MCP server:

grok mcp add --transport http busabase https://busabase.com/api/mcp
grok mcp list

OAuth is handled automatically: a server that requires it triggers a browser sign-in on first use, and tokens are stored under ~/.grok/mcp_credentials.json. The same server can be declared in ~/.grok/config.toml:

[mcp_servers.busabase]
url = "https://busabase.com/api/mcp"

Run grok mcp doctor busabase if a connection fails, then ask Grok to call auth_verify.

Grok Build MCP documentation

Known gotchas

The MCP docs say OAuth is handled automatically and triggers a browser flow on first use, but do not state whether dynamic client registration is used, so auth-mode is left unknown. Grok also loads MCP configurations from `~/.claude.json`, `.cursor/mcp.json` and project `.mcp.json` files, merged below `config.toml` in priority — a server you only configured for another client can appear in Grok too; `grok inspect` shows every loaded server and its origin, and `[compat.claude] mcps = false` / `[compat.cursor] mcps = false` disables a vendor. Access requires a SuperGrok or X Premium+ subscription (early beta). Cold-start `npx` stdio servers may need a higher `startup_timeout_sec` (default 30s).

How it compares

Connection capabilities side by side with other agents already in this directory.

CapabilityGrok BuildClaude CodeCursor
TypeTerminal agentsTerminal agentsAI editors
Recommended pathAgent SkillAgent SkillAgent Skill
How it connectsMCP + OAuth · Plugin / SkillMCP + OAuth · Plugin / SkillMCP + OAuth · Plugin / Skill
TransportStreamable HTTPStreamable HTTPStreamable HTTP
AuthenticationUnknownOAuth (dynamic registration)OAuth (dynamic registration)
These stepsFrom official docsLast checked Nov 9, 2026

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 agent

Paste this into Grok Build

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.