Busabase for Continue

Connect Continue to Busabase

Open-source IDE assistant configured from YAML blocks committed alongside the project.

Paste this into Continue

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 Continue 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.

For this agent

Continue needs its agent/tool mode enabled to run shell commands for the setup steps.

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: Continue
How it connects: MCP + API key · Plugin / Skill
Transport: Streamable HTTP
Authentication: Unknown
Config file: .continue/mcpServers/

Create a YAML file under .continue/mcpServers/ in your workspace:

mcpServers:
  - name: Busabase
    type: streamable-http
    url: https://busabase.com/api/mcp

Continue picks up files in that directory automatically. Then ask the agent to call auth_verify.

Known gotchas

Configuration is file-based (a YAML file under `.continue/mcpServers/`), with no documented UI path for adding a remote server. The docs do not mention OAuth, so plan on an API key.

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 Continue

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 Continue

Connect Continue to Busabase

Open-source IDE assistant configured from YAML blocks committed alongside the project.

Paste this into Continue

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 Continue 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.

For this agent

Continue needs its agent/tool mode enabled to run shell commands for the setup steps.

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: Continue
How it connects: MCP + API key · Plugin / Skill
Transport: Streamable HTTP
Authentication: Unknown
Config file: .continue/mcpServers/

Create a YAML file under .continue/mcpServers/ in your workspace:

mcpServers:
  - name: Busabase
    type: streamable-http
    url: https://busabase.com/api/mcp

Continue picks up files in that directory automatically. Then ask the agent to call auth_verify.

Known gotchas

Configuration is file-based (a YAML file under `.continue/mcpServers/`), with no documented UI path for adding a remote server. The docs do not mention OAuth, so plan on an API key.

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 Continue

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 Continue

Connect Continue to Busabase

Open-source IDE assistant configured from YAML blocks committed alongside the project.

Paste this into Continue

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 Continue 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.

For this agent

Continue needs its agent/tool mode enabled to run shell commands for the setup steps.

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: Continue
How it connects: MCP + API key · Plugin / Skill
Transport: Streamable HTTP
Authentication: Unknown
Config file: .continue/mcpServers/

Create a YAML file under .continue/mcpServers/ in your workspace:

mcpServers:
  - name: Busabase
    type: streamable-http
    url: https://busabase.com/api/mcp

Continue picks up files in that directory automatically. Then ask the agent to call auth_verify.

Known gotchas

Configuration is file-based (a YAML file under `.continue/mcpServers/`), with no documented UI path for adding a remote server. The docs do not mention OAuth, so plan on an API key.

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 Continue

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