Busabase for Kiro

Connect Kiro to Busabase

AWS's agentic IDE — turns natural-language prompts into structured specs and working code, with its own filesystem and terminal.

Paste this into Kiro

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

Kiro is spec-driven: it may want to write a spec before executing. Let it read the setup document first, then approve the commands it proposes.

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: AWS
How it connects: Plugin / Skill · MCP + OAuth
Transport: Streamable HTTP
Authentication: OAuth (dynamic registration)
Config file: .kiro/settings/mcp.json (user: ~/.kiro/settings/mcp.json)

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

Known gotchas

Kiro's main MCP page shows a capability matrix marking remote HTTP/SSE as supported in IDE and CLI, but only demonstrates stdio (`command`/`args`) servers — the remote `url` shape is on the separate Configuration page. Workspace `.kiro/settings/mcp.json` takes precedence over the user-level file, so check both if a stale server keeps loading.

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 Kiro

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 Kiro

Connect Kiro to Busabase

AWS's agentic IDE — turns natural-language prompts into structured specs and working code, with its own filesystem and terminal.

Paste this into Kiro

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

Kiro is spec-driven: it may want to write a spec before executing. Let it read the setup document first, then approve the commands it proposes.

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: AWS
How it connects: Plugin / Skill · MCP + OAuth
Transport: Streamable HTTP
Authentication: OAuth (dynamic registration)
Config file: .kiro/settings/mcp.json (user: ~/.kiro/settings/mcp.json)

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)".

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

Kiro MCP configuration

Known gotchas

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 Kiro

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 Kiro

Connect Kiro to Busabase

AWS's agentic IDE — turns natural-language prompts into structured specs and working code, with its own filesystem and terminal.

Paste this into Kiro

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

Kiro is spec-driven: it may want to write a spec before executing. Let it read the setup document first, then approve the commands it proposes.

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: AWS
How it connects: Plugin / Skill · MCP + OAuth
Transport: Streamable HTTP
Authentication: OAuth (dynamic registration)
Config file: .kiro/settings/mcp.json (user: ~/.kiro/settings/mcp.json)

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)".

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

Kiro MCP configuration

Known gotchas

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 Kiro

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