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.

KiroAmp
MakerAWSAmp
LicenseProprietaryProprietary
ModelsSee vendor docsSee vendor docs
Runs inIDE, CLITerminal, IDE
MCPMCP: supportedMCP: supported
Agent SkillsAgent Skills: supportedAgent Skills: supported
AGENTS.md?AGENTS.md: not yet verifiedAGENTS.md: supported
ACPACP: 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

Kiro

Spec-driven agentic IDE and CLI: turns prompts into requirements, designs and tasks before writing code.

Amp

Frontier coding agent for terminal and editor. Co-created the AGENTS.md convention and supports Agent Skills.

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.