Busabase for Kilo Code

Connect Kilo Code to Busabase

Open-source VS Code coding agent that starts the OAuth 2.0 flow automatically for remote MCP servers.

Paste this into Kilo Code

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 Kilo Code Skills documentation

Busabase

Agent Skill

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.

Install the Busabase skills

npx skills add busabase/skills

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.

Kilo Code MCP documentation

At a glance

Vendor: Kilo Code
How it connects: MCP + OAuth · Plugin / Skill
Transport: Streamable HTTP
Authentication: OAuth (dynamic registration)
Config file: ~/.config/kilo/kilo.json (kilo.jsonc also supported; project: .kilo/kilo.json)

Use Settings → MCP → Add Server → Remote (HTTP), or edit ~/.config/kilo/kilo.jsonc (project: .kilo/kilo.jsonc):

{
  "mcp": {
    "busabase": {
      "type": "remote",
      "url": "https://busabase.com/api/mcp",
      "enabled": true
    }
  }
}

Kilo Code starts the OAuth flow on connect. Complete it in the browser, then ask the agent to call auth_verify.

To sign in (or re-sign in) from the terminal, run kilo auth busabase (also available as kilo mcp auth busabase); kilo mcp auth list shows which servers still need authentication. If a sign-in stalls, kilo mcp debug busabase prints the discovered OAuth endpoints and the exact callback URL Kilo registers.

Known gotchas

The config block is `mcp` with `"type": "remote"` — not the `mcpServers` shape most other clients use. OAuth runs automatically; only set `"oauth": false` if you deliberately want header auth instead. The OAuth block takes clientId, clientSecret, scope (a single string), callbackPort and redirectUri; the local callback defaults to port 19876 (http://127.0.0.1:19876/mcp/oauth/callback). The CLI docs now recommend the kilo.json filename; kilo.jsonc remains supported.

How it compares

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

Capability	Kilo Code	Claude Code	Cursor
Type	IDE plugins	Terminal agents	AI editors
Recommended path	Agent Skill	Agent Skill	Agent Skill
How it connects	MCP + OAuth · Plugin / Skill	MCP + OAuth · Plugin / Skill	MCP + OAuth · Plugin / Skill
Transport	Streamable HTTP	Streamable HTTP	Streamable HTTP
Authentication	OAuth (dynamic registration)	OAuth (dynamic registration)	OAuth (dynamic registration)

These stepsFrom official docsLast checked Nov 10, 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.

Where these steps come from Official site

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 Kilo Code

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