The interface layer for the agent era
CLIs are how AI agents get work done
The difference between chat and action is tools. CLIs let AI agents inspect systems, make changes, and verify the result.
See it in action:
What builders are saying
Real signals from people actually building agent-native tools.
unpopular (maybe?) opinion: MCP is dead in the water. […] api & cli will win. […] connect 10 servers with 5 tools each and you've burned 50 tool definitions worth of tokens before your conversation even starts. […] the "exec" tool paired with on-demand skills is all you need.
MCP is dead? […] I mostly use Skills and CLI lately.
Then we'll release the new agent-optimized CLI for Basecamp. Love to see agents drive their own accommodations.
CLIs are super exciting precisely because they are a "legacy" technology, which means AI agents can natively and easily use them, combine them, interact with them via the entire terminal toolkit. […] It's 2026. Build. For. Agents.
Introducing the Google Workspace CLI […] built for humans and agents. Google Drive, Gmail, Calendar, and every Workspace API. 40+ agent skills included.
2026 is the year of Skills & CLIs
This is why I'm not a fan of MCP, it speaks only to machines. Better CLI tooling, output formatting, docs helps both machines and humans.
Companies that market to developers will soon start “marketing” to coding agents as well. [...] Agent-friendly UI/UX (often: a good CLI) will be prioritized.
I tried with an MCP first but now I just use the CLI.
[…] I find CLI tools are almost always a better bet than MCPs when you have an unleashed coding agent like Claude Code in YOLO mode
there's a reason I didn't add mcp support to openclaw (except via mcporter mcp-to-cli converter)
Convert chrome-devtools (or really any) MCP to compiled cli […] It will call help menu and learn as needed. Progressive disclosure, no context pollution.
CLI is the rare interface where making things better for agents makes things better for humans too. And vice versa.
It's time for you to think about how an agent can use your app via CLI. In the future, none of us (including our agents) are going to want to log in to a web interface to do anything.
unpopular (maybe?) opinion: MCP is dead in the water. […] api & cli will win. […] connect 10 servers with 5 tools each and you've burned 50 tool definitions worth of tokens before your conversation even starts. […] the "exec" tool paired with on-demand skills is all you need.
MCP is dead? […] I mostly use Skills and CLI lately.
Then we'll release the new agent-optimized CLI for Basecamp. Love to see agents drive their own accommodations.
CLIs are super exciting precisely because they are a "legacy" technology, which means AI agents can natively and easily use them, combine them, interact with them via the entire terminal toolkit. […] It's 2026. Build. For. Agents.
Introducing the Google Workspace CLI […] built for humans and agents. Google Drive, Gmail, Calendar, and every Workspace API. 40+ agent skills included.
2026 is the year of Skills & CLIs
This is why I'm not a fan of MCP, it speaks only to machines. Better CLI tooling, output formatting, docs helps both machines and humans.
Companies that market to developers will soon start “marketing” to coding agents as well. [...] Agent-friendly UI/UX (often: a good CLI) will be prioritized.
I tried with an MCP first but now I just use the CLI.
[…] I find CLI tools are almost always a better bet than MCPs when you have an unleashed coding agent like Claude Code in YOLO mode
there's a reason I didn't add mcp support to openclaw (except via mcporter mcp-to-cli converter)
CLI is the rare interface where making things better for agents makes things better for humans too. And vice versa.
It's time for you to think about how an agent can use your app via CLI. In the future, none of us (including our agents) are going to want to log in to a web interface to do anything.
unpopular (maybe?) opinion: MCP is dead in the water. […] api & cli will win. […] connect 10 servers with 5 tools each and you've burned 50 tool definitions worth of tokens before your conversation even starts. […] the "exec" tool paired with on-demand skills is all you need.
unpopular (maybe?) opinion: MCP is dead in the water. […] api & cli will win. […] connect 10 servers with 5 tools each and you've burned 50 tool definitions worth of tokens before your conversation even starts. […] the "exec" tool paired with on-demand skills is all you need.
MCP is dead? […] I mostly use Skills and CLI lately.
Then we'll release the new agent-optimized CLI for Basecamp. Love to see agents drive their own accommodations.
CLIs are super exciting precisely because they are a "legacy" technology, which means AI agents can natively and easily use them, combine them, interact with them via the entire terminal toolkit. […] It's 2026. Build. For. Agents.
Introducing the Google Workspace CLI […] built for humans and agents. Google Drive, Gmail, Calendar, and every Workspace API. 40+ agent skills included.
2026 is the year of Skills & CLIs
This is why I'm not a fan of MCP, it speaks only to machines. Better CLI tooling, output formatting, docs helps both machines and humans.
Companies that market to developers will soon start “marketing” to coding agents as well. [...] Agent-friendly UI/UX (often: a good CLI) will be prioritized.
I tried with an MCP first but now I just use the CLI.
[…] I find CLI tools are almost always a better bet than MCPs when you have an unleashed coding agent like Claude Code in YOLO mode
there's a reason I didn't add mcp support to openclaw (except via mcporter mcp-to-cli converter)
Convert chrome-devtools (or really any) MCP to compiled cli […] It will call help menu and learn as needed. Progressive disclosure, no context pollution.
CLI is the rare interface where making things better for agents makes things better for humans too. And vice versa.
It's time for you to think about how an agent can use your app via CLI. In the future, none of us (including our agents) are going to want to log in to a web interface to do anything.
unpopular (maybe?) opinion: MCP is dead in the water. […] api & cli will win. […] connect 10 servers with 5 tools each and you've burned 50 tool definitions worth of tokens before your conversation even starts. […] the "exec" tool paired with on-demand skills is all you need.
MCP is dead? […] I mostly use Skills and CLI lately.
Then we'll release the new agent-optimized CLI for Basecamp. Love to see agents drive their own accommodations.
CLIs are super exciting precisely because they are a "legacy" technology, which means AI agents can natively and easily use them, combine them, interact with them via the entire terminal toolkit. […] It's 2026. Build. For. Agents.
Introducing the Google Workspace CLI […] built for humans and agents. Google Drive, Gmail, Calendar, and every Workspace API. 40+ agent skills included.
2026 is the year of Skills & CLIs
This is why I'm not a fan of MCP, it speaks only to machines. Better CLI tooling, output formatting, docs helps both machines and humans.
Companies that market to developers will soon start “marketing” to coding agents as well. [...] Agent-friendly UI/UX (often: a good CLI) will be prioritized.
I tried with an MCP first but now I just use the CLI.
[…] I find CLI tools are almost always a better bet than MCPs when you have an unleashed coding agent like Claude Code in YOLO mode
there's a reason I didn't add mcp support to openclaw (except via mcporter mcp-to-cli converter)
CLI is the rare interface where making things better for agents makes things better for humans too. And vice versa.
It's time for you to think about how an agent can use your app via CLI. In the future, none of us (including our agents) are going to want to log in to a web interface to do anything.
unpopular (maybe?) opinion: MCP is dead in the water. […] api & cli will win. […] connect 10 servers with 5 tools each and you've burned 50 tool definitions worth of tokens before your conversation even starts. […] the "exec" tool paired with on-demand skills is all you need.
Or skip the search — install the agent skill · api/clis
Google's open-source terminal AI agent for coding, automation, repository work, and structured command-line workflows.
Anthropic's terminal-native coding agent for repo understanding, edits, tests, and git workflows.
OpenAI's lightweight terminal coding agent for editing, running tasks, and agentic development loops.
AI pair programming CLI that edits code, runs tests, and collaborates on existing repos directly in the terminal.
Open-source on-machine AI agent from Block for coding, execution, debugging, and multi-step developer workflows.
Open-source terminal coding agent focused on fast local loops, tool orchestration, and AI-assisted development.
Official AWS coding agent CLI for terminal chat, code tasks, and agentic developer workflows.
Why CLIs?
The interface layer for AI agents
AI agents don't click buttons — they run commands. A single CLI call uses ~200 tokens. The equivalent MCP server dumps 55,000 tokens into your context window. That's a 275x difference →