Developer shares CLI tools that work well with Claude Code

Switching from MCPs to CLIs for Claude Code

A developer on r/ClaudeAI shared their experience switching from MCPs (Model Context Protocols) to CLIs when working with Claude Code. They initially used MCPs but found them frustrating due to parameter errors, authentication issues, timeouts, and slower performance.

The developer discovered that Claude handles CLI commands effectively because it has been trained on years of shell scripts, documentation, Stack Overflow answers, and GitHub issues. Claude knows command flags, edge cases, and can compose commands in ways that would take the developer significant time to figure out manually.

Daily CLI tools used with Claude Code

The developer shared the specific command-line tools they use in their daily workflow with Claude Code:

• gh (GitHub CLI) – For PRs, issues, code search, and other GitHub operations. They use the --json flag with --jq for precise output. Claude can chain commands for workflows like creating issues, assigning them, opening PRs, and requesting reviews.
• ripgrep – For fast code search across large repositories, which they find better than standard grep. Claude uses it to find symbols, trace usage, and navigate unfamiliar codebases.
• stripe – For webhook testing, event triggering, and log tailing. The --output json flag makes it agent-friendly, saving manual work on payment flows.
• supabase – For local development, database management, and edge functions. Claude knows this CLI well and can run commands like supabase start plus database commands to set up local environments.
• vercel – For deployment, environment variable management, and domain management. Token-based authentication (vercel --token $TOKEN) works without browser interaction.
• sentry-cli – For release management, source maps, and log tailing. The --format json flag throughout allows Claude to diagnose errors without manual stack trace copying.
• neon – For Postgres branch management from the terminal. Claude can spin up branches, test migrations, and tear them down, which helps avoid production issues.

The developer is compiling a list of CLIs that work well with Claude Code, focusing on those with structured output, non-interactive mode, and API key authentication. They're seeking additional CLI recommendations from the community.