Comparison
goose vs Amp
How the two compare on the things that decide whether your setup carries over: open standards, license, models and where they run.
| goose | Amp | |
|---|---|---|
| Maker | Block, now at the Agentic AI Foundation | Amp |
| License | Apache-2.0 | Proprietary |
| Models | Many providers, including local models | See vendor docs |
| Runs in | Desktop, Terminal, API | Terminal, IDE |
| MCP | MCP: supported | MCP: supported |
| Agent Skills | Agent Skills: supported | Agent Skills: supported |
| AGENTS.md | AGENTS.md: supported | AGENTS.md: supported |
| ACP | ACP: supported | ?ACP: not yet verified |
Key differences
- goose is open source (Apache-2.0); Amp is proprietary. If you need to self-host, audit or fork the harness, that settles it.
- goose also runs in Desktop, API; Amp also runs in IDE.
- goose supports ACP; we have not verified it for Amp.
- Both support MCP, Agent Skills, AGENTS.md, so MCP servers, skills and repo instructions you set up carry over if you switch.
In their own words
FAQ
- Is goose or Amp open source?
- goose is open source under Apache-2.0. Amp is proprietary.
- Do goose and Amp support MCP servers?
- goose: yes. Amp: yes.
- Can I reuse Agent Skills between goose 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.