Comparison

Kiro vs Factory Droid

How the two compare on the things that decide whether your setup carries over: open standards, license, models and where they run.

KiroFactory Droid
MakerAWSFactory
LicenseProprietaryProprietary
ModelsSee vendor docsSee vendor docs
Runs inIDE, CLITerminal, IDE, CI/CD
MCPMCP: supportedMCP: supported
Agent SkillsAgent Skills: supportedAgent Skills: supported
AGENTS.md?AGENTS.md: not yet verifiedAGENTS.md: supported
ACPACP: supportedACP: supported

Key differences

  • Both are proprietary products from their vendors.
  • Kiro also runs in CLI; Factory Droid also runs in Terminal, CI/CD.
  • Factory Droid supports AGENTS.md; we have not verified it for Kiro.
  • Both support MCP, Agent Skills, ACP, 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.

Factory Droid

Delegates whole tasks (refactors, migrations, incident response) to Droids from IDE, CLI or CI/CD.

FAQ

Is Kiro or Factory Droid open source?
Kiro is proprietary. Factory Droid is proprietary.
Do Kiro and Factory Droid support MCP servers?
Kiro: yes. Factory Droid: yes.
Can I reuse Agent Skills between Kiro and Factory Droid?
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.