Busabase

Integration Overview

Choose how to connect to Busabase through the browser, CLI, SDK, MCP, OpenAPI, agent skills, events, automation, or imports.

Connect to the same workspace from whichever tool fits your work. You can combine methods: an agent proposes changes through MCP, a person reviews in the browser, and a script reads approved records through the SDK.

Choose a method

The Channel column in Insights records how a contribution arrived. Follow its link to the matching guide.

ChannelUse it forStart here
Web UI (web_ui) / Browser (browser)Browse, edit, and review in your browserBrowser quick start
CLI (cli)Terminal work, scripts, and CIInstall and connect the CLI
SDK (sdk)TypeScript / JavaScript applicationsInstall and use the SDK
MCP (mcp)Give your agent tools through its MCP clientMCP connection and OAuth
OpenAPI (openapi)HTTP integrations in any languageOpenAPI and REST
Skill (skill)Teach your agent the Busabase workflowInstall agent skills
Webhook (webhook)React to workspace eventsWebhooks and events
Automation (automation)Run a recurring or event-driven workflowAutomation
Import (import)Bring in a package or restore a backupImport

Skills teach an agent how to work; CLI, MCP, and HTTP provide the connection it uses. A webhook sends an event to another system, which can then use CLI, SDK, or REST to act on the workspace.

Automation

For a recurring job, run the CLI, SDK, or REST API from your own scheduler or CI workflow. For event-driven work, configure Webhooks and events. The automation channel identifies a contribution's source; it does not configure a schedule.

Start with read-only calls, verify the target workspace, and use Change Requests when your workflow proposes edits. Grant only the permissions it needs in API Tokens.

Import

To install a reusable workspace package from GitHub, follow Install and export, preview what it will create, and review its proposed content. To restore a full backup into an empty workspace, follow Busabase dump.

Verify your connection

For Cloud, choose the account, API key or OAuth grant, and target workspace before reading or writing. The CLI guide covers sign-in and workspace selection; SDK and REST use the same base URL, key, and workspace id. Local and self-hosted connection details are documented in each guide.

Other ways to connect: Integration overview · CLI · SDK · MCP · OpenAPI / REST · Agent Skills · Webhooks

On this page