Kiro is an agentic IDE with its own filesystem and terminal, so the Skill path applies: paste the prompt above and Kiro connects itself.

Prefer a connector?

Kiro reads MCP servers from .kiro/settings/mcp.json (workspace) or ~/.kiro/settings/mcp.json (user). Workspace settings take precedence when both exist.

{
  "mcpServers": {
    "busabase": {
      "url": "https://busabase.com/api/mcp"
    }
  }
}

Only url is mandatory for a remote server — Kiro's docs describe it as the "HTTPS endpoint for the remote MCP server (or HTTP endpoint for localhost)".

Kiro's config also accepts an oauth object (clientId, clientSecret, redirectUri, oauthScopes), but Busabase supports dynamic client registration, so you should not need to pre-register anything — the docs state that Kiro handles the browser-based OAuth flow automatically.

Optional keys on the same entry: headers, disabled, autoApprove, disabledTools.

Kiro MCP configuration