Conectar Kiro a Busabase

curl -fsSL https://cli.kiro.dev/install | bash      # Kiro CLI, macOS/Linux
irm 'https://cli.kiro.dev/install.ps1' | iex       # Kiro CLI, Windows 11
# Kiro IDE: download from https://kiro.dev

Kiro — the IDE or the Kiro CLI — can fetch a URL and run commands, so the Skill path applies: paste the prompt above.

Prefer a connector?

Add Busabase to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace, which wins when both define the same server):

{
  "mcpServers": {
    "busabase": {
      "url": "https://busabase.com/api/mcp",
      "oauth": {
        "oauthScopes": ["mcp"]
      }
    }
  }
}

Kiro registers its own OAuth client (dynamic client registration) and opens the sign-in page in your browser. Keep the entry's oauth.oauthScopes set to ["mcp"]: Busabase grants MCP clients exactly one scope, mcp, and a request naming a different Busabase scope without it is rejected.

Kiro CLI: kiro-cli mcp add only takes a --command for local servers, so edit the JSON file above or use kiro-cli mcp import --file <file>. In a kiro-cli chat session, open /mcp and press Enter on busabase to start sign-in; /mcp auth busabase retries it.

Coming from the Amazon Q Developer CLI? Installing Kiro CLI copies ~/.aws/amazonq/mcp.json to ~/.kiro/settings/mcp.json once, so an existing busabase entry carries over. Anything added to the old file afterwards is not picked up.

Kiro MCP configuration