Comparison

Gemini CLI vs Kiro

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

Gemini CLIKiro
MakerGoogleAWS
LicenseApache-2.0Proprietary
ModelsGoogle Gemini modelsSee vendor docs
Runs inTerminalIDE, CLI
MCPMCP: supportedMCP: supported
Agent SkillsAgent Skills: supportedAgent Skills: supported
AGENTS.mdAGENTS.md: supported?AGENTS.md: not yet verified
ACPACP: supportedACP: supported

Key differences

  • Gemini CLI is open source (Apache-2.0); Kiro is proprietary. If you need to self-host, audit or fork the harness, that settles it.
  • Gemini CLI also runs in Terminal; Kiro also runs in IDE, CLI.
  • Gemini CLI 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

Gemini CLI

Google's open-source terminal agent for Gemini models, with MCP servers, extensions, Skills and AGENTS.md support.

Kiro

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

FAQ

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