Busabase for Cline

Connect Cline to Busabase

Open-source autonomous coding extension for VS Code and JetBrains, with its own Remote Servers tab for MCP.

Paste this into Cline

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 Cline 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

Cline asks for approval per command by default. Approve the setup steps, or enable auto-approve for the session.

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: Cline
How it connects: MCP + API key · Plugin / Skill
Transport: Streamable HTTP
Authentication: API key
Config file: ~/.cline/mcp.json

Add Busabase to ~/.cline/mcp.json (CLI), or use the stacked-server icon → Remote Servers → Add Server in the IDE extension:

{
  "mcpServers": {
    "busabase": {
      "type": "streamableHttp",
      "url": "https://busabase.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_BUSABASE_API_KEY>"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

In the IDE, pick Streamable HTTP as the transport type. Then ask the agent to call auth_verify.

Create the API key at a changeRequest permission level so Cline can propose changes but never merge them itself.

Known gotchas

Cline's docs describe header-based auth rather than OAuth, so use a Busabase API key in the `headers` block. Set `"type": "streamableHttp"` explicitly instead of relying on the default.

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 Cline

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 Cline

Connect Cline to Busabase

Open-source autonomous coding extension for VS Code and JetBrains, with its own Remote Servers tab for MCP.

Paste this into Cline

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 Cline 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

Cline asks for approval per command by default. Approve the setup steps, or enable auto-approve for the session.

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: Cline
How it connects: MCP + API key · Plugin / Skill
Transport: Streamable HTTP
Authentication: API key
Config file: ~/.cline/mcp.json

Add Busabase to ~/.cline/mcp.json (CLI), or use the stacked-server icon → Remote Servers → Add Server in the IDE extension:

{
  "mcpServers": {
    "busabase": {
      "type": "streamableHttp",
      "url": "https://busabase.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_BUSABASE_API_KEY>"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

In the IDE, pick Streamable HTTP as the transport type. Then ask the agent to call auth_verify.

Create the API key at a changeRequest permission level so Cline can propose changes but never merge them itself.

Known gotchas

Cline's docs describe header-based auth rather than OAuth, so use a Busabase API key in the `headers` block. Set `"type": "streamableHttp"` explicitly instead of relying on the default.

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 Cline

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 Cline

Connect Cline to Busabase

Open-source autonomous coding extension for VS Code and JetBrains, with its own Remote Servers tab for MCP.

Paste this into Cline

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 Cline 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

Cline asks for approval per command by default. Approve the setup steps, or enable auto-approve for the session.

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: Cline
How it connects: MCP + API key · Plugin / Skill
Transport: Streamable HTTP
Authentication: API key
Config file: ~/.cline/mcp.json

Add Busabase to ~/.cline/mcp.json (CLI), or use the stacked-server icon → Remote Servers → Add Server in the IDE extension:

{
  "mcpServers": {
    "busabase": {
      "type": "streamableHttp",
      "url": "https://busabase.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_BUSABASE_API_KEY>"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

In the IDE, pick Streamable HTTP as the transport type. Then ask the agent to call auth_verify.

Create the API key at a changeRequest permission level so Cline can propose changes but never merge them itself.

Known gotchas

Cline's docs describe header-based auth rather than OAuth, so use a Busabase API key in the `headers` block. Set `"type": "streamableHttp"` explicitly instead of relying on the default.

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 Cline

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