MCP.so
Sign In

CLI

A curated directory of product CLIs, developer tools, and terminal apps — verified for humans, scripts, and AI agents.

Frequently asked questions

Common questions about CLI tools, Agent CLIs, and command line automation

1

What is a CLI?

A CLI, or command-line interface, lets you control software by typing commands in a terminal instead of clicking through a graphical interface. CLI tools are useful for development, automation, scripts, CI pipelines, and repeatable operations.

2

What is an Agent CLI?

An Agent CLI is either a command-line tool for operating an AI agent or a conventional CLI designed to be called reliably by AI agents. Agent-friendly CLIs expose clear commands, non-interactive options, predictable output, and meaningful exit codes so an agent can plan, execute, and verify work.

3

Can Claude Code, Codex, Cursor, and other AI agents use these CLI tools?

Yes. AI coding agents can invoke many of these CLIs through a shell to work with repositories, cloud services, databases, productivity apps, and deployment systems. Tools marked Agent-ready are especially suitable for scripted or autonomous use, but authentication and permissions still need to be configured safely.

4

What makes a CLI suitable for AI agents?

The best CLI tools for AI agents support non-interactive commands, stable flags, structured or parseable output, standard input and output, documented authentication, and reliable exit codes. These features make results easier for an agent to interpret and verify without manual intervention.

5

Should I use an official CLI or a community CLI?

Choose an official CLI when you need first-party support, close alignment with a service API, and predictable updates. A community CLI can be a better fit when it offers a simpler workflow or capabilities the official tool lacks. Review its repository, maintenance activity, permissions, and installation instructions before use.