MCP.so
Sign In

CLI

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

AI agents

>_

GitHub Copilot CLI

$ copilot

Official

GitHub’s terminal coding agent for planning, editing, running, and reviewing changes with repository context.

AI agentsAgent-ready
>_

LLM

$ llm

Official

Run prompts, manage models, and extend LLM providers with plugins.

AI agentsAgent-ready
>_

Ollama

$ ollama

Official

Run and manage open models locally through a simple command-line interface.

AI agentsAgent-ready
>_

AIChat

$ aichat

Official

Chat with multiple AI providers, roles, sessions, tools, and local models.

AI agentsAgent-ready
>_

Aider

$ aider

Official

An open-source AI pair programmer that edits code in a local Git repository with many model providers.

AI agentsAgent-ready
>_

Amazon Q Developer CLI

$ q

Official

AWS’s terminal assistant for coding, shell completion, natural-language workflows, and AWS development.

AI agentsAgent-ready
>_

Claude Code

$ claude

Official

Anthropic’s agentic coding tool for understanding codebases, editing files, and automating terminal workflows.

AI agentsAgent-ready
>_

Continue CLI

$ cn

Official

Run Continue coding-agent workflows from terminals and CI environments.

AI agentsAgent-ready
>_

Fabric

$ fabric

Official

Apply reusable AI patterns to summarization, extraction, and research tasks.

AI agentsAgent-ready
>_

Gemini CLI

$ gemini

Official

Google’s open-source terminal agent with Gemini models, tools, MCP support, and project context.

AI agentsAgent-ready
>_

Goose

$ goose

Official

An open-source extensible AI agent that installs, executes, edits, and tests through terminal tools and MCP.

AI agentsAgent-ready
>_

Hugging Face CLI

$ hf

Official

Authenticate with the Hugging Face Hub, download and upload models, manage repositories, and run jobs.

AI agentsAgent-ready
>_

Open Interpreter

$ interpreter

Official

Use natural language to run code and complete computer tasks locally.

AI agentsAgent-ready
>_

OpenAI Codex CLI

$ codex

Official

OpenAI’s coding agent for reading, changing, and running code directly from the terminal.

AI agentsAgent-ready
>_

OpenCode

$ opencode

Official

An open-source terminal coding agent with multiple model providers, sessions, tools, and LSP integration.

AI agentsAgent-ready
>_

Qwen Code

$ qwen

Official

Qwen’s open-source terminal coding agent with repository tools, non-interactive mode, and MCP support.

AI agentsAgent-ready

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.

6

How should I protect credentials and permissions when using CLI tools?

Use an OS keychain, environment variables, or a dedicated secret store instead of placing API keys in repositories, prompts, or shell history. Give people and AI agents least-privilege access, start in read-only or test environments, and confirm that automated commands support previews, explicit confirmation controls, and reliable exit codes.