the integrations

Kiro CLI (the Amazon Q Developer CLI rebrand)

null

{"id":"kiro","name":"Kiro CLI (the Amazon Q Developer CLI rebrand)","class":"B","status":"recon","install":"add nika to ~/.kiro/settings/mcp.json (mcpServers map · the legacy ~/.aws/amazonq/mcp.json is still read, .kiro wins)","wire":"kiro","components":{"mcp":"mcp-config"},"gaps":[],"class_gap":"no AGENTS.md read documented (steering files are their mechanism) · MCP carries the oracle"}

Recon: the client is mapped, and nothing is wired yet. Class B: no plugin loader, so MCP and the scaffold carry the teaching.

reconthe stateat v0.107.0
Bthe classhow much lands
1piece landsnamed below
0gapsnothing missing

get set up

add nika to ~/.kiro/settings/mcp.json (mcpServers map · the legacy ~/.aws/amazonq/mcp.json is still read, .kiro wins)

The binary writes that itself: nika wire kiro puts the oracle where this client looks for it, and nika doctor says so when the two fall out of step.

what lands, and how

mcpmcp-config

what does not

no AGENTS.md read documented (steering files are their mechanism) · MCP carries the oracle

cross-references

the rooms it touches

where this comes from

v0.107.0
kiro