MCP.so
Sign In

CLI

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

Terminal apps

>_

Yazi

$ yazi

Official

An asynchronous terminal file manager with rich previews and plugins.

Terminal apps
>_

btop

$ btop

Official

A resource monitor for CPU, memory, disks, network, and processes.

Terminal apps
>_

fzf

$ fzf

Official

A general-purpose fuzzy finder for files, history, processes, and more.

Terminal appsAgent-ready
>_

ripgrep

$ rg

Official

Recursively search files with fast regex matching and gitignore support.

Terminal appsAgent-ready
>_

tmux

$ tmux

Official

A terminal multiplexer for persistent sessions, panes, and windows.

Terminal apps
>_

Atuin

$ atuin

Official

Search, sync, and understand shell history with rich execution context.

Terminal apps
>_

Fish Shell

$ fish

Official

A user-friendly shell with suggestions, highlighting, and practical defaults.

Terminal apps
>_

Helix

$ hx

Official

A modal terminal editor with built-in LSP and tree-sitter support.

Terminal apps
>_

Mosh

$ mosh

Official

A roaming remote shell that survives network changes and intermittent links.

Terminal apps
>_

Starship

$ starship

Official

A fast customizable prompt for every major shell.

Terminal apps
>_

aria2

$ aria2c

Official

A lightweight multi-protocol download utility with parallel transfers.

Terminal appsAgent-ready
>_

asciinema

$ asciinema

Official

Record, replay, and share terminal sessions as lightweight text.

Terminal apps
>_

bat

$ bat

Official

A cat replacement with syntax highlighting, paging, and Git integration.

Terminal appsAgent-ready
>_

bottom

$ btm

Official

A customizable cross-platform graphical process and system monitor.

Terminal apps
>_

broot

$ broot

Official

Navigate directory trees, preview files, and launch commands interactively.

Terminal apps
>_

duf

$ duf

Official

Show filesystem usage with readable tables, colors, and filters.

Terminal appsAgent-ready
>_

dust

$ dust

Official

Visualize disk usage as an intuitive tree from the command line.

Terminal appsAgent-ready
>_

eza

$ eza

Official

A modern ls replacement with Git status, colors, icons, and tree views.

Terminal apps
>_

fd

$ fd

Official

A fast and user-friendly alternative to the traditional find command.

Terminal appsAgent-ready
>_

ncdu

$ ncdu

Official

Analyze disk usage with a fast interactive terminal interface.

Terminal apps
>_

nnn

$ nnn

Official

A fast terminal file manager with plugins and desktop integration.

Terminal apps
>_

procs

$ procs

Official

A modern ps replacement with search, trees, and useful columns.

Terminal appsAgent-ready
>_

ranger

$ ranger

Official

A console file manager with Vi key bindings and previews.

Terminal apps
>_

tldr

$ tldr

Official

Community-maintained command documentation focused on practical examples.

Terminal apps
>_

tmate

$ tmate

Official

Share a live terminal session securely for pairing and support.

Terminal apps
>_

trash-cli

$ trash

Official

Move files to the system trash instead of deleting them permanently.

Terminal appsAgent-ready
>_

zoxide

$ zoxide

Official

A smarter cd command that learns the directories you use most.

Terminal apps

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.