Comparison
Kiro vs Amp
How the two compare on the things that decide whether your setup carries over: open standards, license, models and where they run.
| Kiro | Amp | |
|---|---|---|
| Maker | AWS | Amp |
| License | Proprietary | Proprietary |
| Models | See vendor docs | See vendor docs |
| Runs in | IDE, CLI | Terminal, IDE |
| MCP | MCP: supported | MCP: supported |
| Agent Skills | Agent Skills: supported | Agent Skills: supported |
| AGENTS.md | ?AGENTS.md: not yet verified | AGENTS.md: supported |
| ACP | ACP: supported | ?ACP: not yet verified |
Key differences
- Both are proprietary products from their vendors.
- Kiro also runs in CLI; Amp also runs in Terminal.
- Amp supports AGENTS.md; we have not verified it for Kiro.
- Kiro supports ACP; we have not verified it for Amp.
- Both support MCP, Agent Skills, so MCP servers, skills and repo instructions you set up carry over if you switch.
In their own words
FAQ
- Is Kiro or Amp open source?
- Kiro is proprietary. Amp is proprietary.
- Do Kiro and Amp support MCP servers?
- Kiro: yes. Amp: yes.
- Can I reuse Agent Skills between Kiro and Amp?
- Yes. Both read the open Agent Skills (SKILL.md) format, so the same skill folder works in both.
Set up MCP servers in either one
More comparisons
Reviewed Oct 5, 2026.