Connect Kiro to Busabase
AWS's agentic coding tool: the Kiro IDE turns prompts into specs and working code, and the Kiro CLI, formerly the Amazon Q Developer CLI, brings the same agent to the 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.

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.
For this agent
Kiro is spec-driven: it may want to write a spec before executing, so let it read the setup document first, then approve the commands it proposes. The skills installer targets Kiro as `kiro-cli` and writes to `~/.kiro/skills`, which both the Kiro IDE and the Kiro CLI read. Custom agents only load skills listed in their `resources` with `skill://`.
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)
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.devKiro — 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"
}
}
}
Kiro registers its own OAuth client (dynamic client registration) and opens the sign-in page in your browser.
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.
Known gotchas
`kiro-cli mcp add` has no URL option, so remote servers go in the JSON file. Workspace `.kiro/settings/mcp.json` overrides the user file, so check both if a stale server keeps loading. Kiro's main MCP page only demonstrates stdio servers; the remote `url` shape is on the Configuration page.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | |||
|---|---|---|---|
| Type | AI editors | Terminal agents | AI editors |
| Recommended path | Agent Skill | Agent Skill | Agent Skill |
| How it connects | Plugin / Skill · MCP + OAuth | 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) |
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.
Let your agent do the setup
One instruction, reviewed access, and every change it makes afterwards arrives as a proposal you approve.
Browse every agentPaste 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.