Busabase for Buda Agent

Connect Buda Agent to Busabase

Buda ships a built-in Busabase integration — connect it under Settings → Integrations, with no URL or config file to edit.

Paste this into Buda Agent

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 Buda Agent documentation

Busabase

Agent Skill

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.

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: Buda
How it connects: MCP + OAuth · Plugin / Skill
Transport: Streamable HTTP
Authentication: OAuth (dynamic registration)

Buda has a built-in Busabase integration, so no URL or JSON file is needed:

Open Settings → Integrations in Buda.
Choose the agent that should receive the connection.
Select Busabase and choose Connect.
Sign in to the intended Busabase account, choose the permission grant, and approve.
Return to Buda and confirm the integration shows Connected.
Ask the agent to call auth_verify and confirm the target space.

Disconnect the integration in Buda before reconnecting if you need to change the Busabase account or permission grant.

Known gotchas

Disconnect the integration in Buda before reconnecting if you need to change the Busabase account or permission grant.

These stepsFrom official docsNo check date recorded

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.

Where these steps come from Official site

Let your agent do the setup

One instruction, reviewed access, and every change it makes afterwards arrives as a proposal you approve.

Browse every agent

Paste this into Buda Agent

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

All agents

Busabase for Buda Agent

Connect Buda Agent to Busabase

Buda ships a built-in Busabase integration — connect it under Settings → Integrations, with no URL or config file to edit.

Paste this into Buda Agent

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 Buda Agent documentation

Busabase

Agent Skill

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.

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: Buda
How it connects: MCP + OAuth · Plugin / Skill
Transport: Streamable HTTP
Authentication: OAuth (dynamic registration)

Buda has a built-in Busabase integration, so no URL or JSON file is needed:

Open Settings → Integrations in Buda.
Choose the agent that should receive the connection.
Select Busabase and choose Connect.
Sign in to the intended Busabase account, choose the permission grant, and approve.
Return to Buda and confirm the integration shows Connected.
Ask the agent to call auth_verify and confirm the target space.

Disconnect the integration in Buda before reconnecting if you need to change the Busabase account or permission grant.

Known gotchas

Disconnect the integration in Buda before reconnecting if you need to change the Busabase account or permission grant.

These stepsFrom official docsNo check date recorded

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.

Where these steps come from Official site

Let your agent do the setup

One instruction, reviewed access, and every change it makes afterwards arrives as a proposal you approve.

Browse every agent

Paste this into Buda Agent

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

All agents

Busabase for Buda Agent

Connect Buda Agent to Busabase

Buda ships a built-in Busabase integration — connect it under Settings → Integrations, with no URL or config file to edit.

Paste this into Buda Agent

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 Buda Agent documentation

Busabase

Agent Skill

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.

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: Buda
How it connects: MCP + OAuth · Plugin / Skill
Transport: Streamable HTTP
Authentication: OAuth (dynamic registration)

Buda has a built-in Busabase integration, so no URL or JSON file is needed:

Open Settings → Integrations in Buda.
Choose the agent that should receive the connection.
Select Busabase and choose Connect.
Sign in to the intended Busabase account, choose the permission grant, and approve.
Return to Buda and confirm the integration shows Connected.
Ask the agent to call auth_verify and confirm the target space.

Disconnect the integration in Buda before reconnecting if you need to change the Busabase account or permission grant.

Known gotchas

Disconnect the integration in Buda before reconnecting if you need to change the Busabase account or permission grant.

These stepsFrom official docsNo check date recorded

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.

Where these steps come from Official site

Let your agent do the setup

One instruction, reviewed access, and every change it makes afterwards arrives as a proposal you approve.

Browse every agent

Paste this into Buda Agent

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