Skip to content
BSWEN
Blog

CLI vs MCP for AI Agents: Why Reddit Developers Say CLI is All You Need

Cowrie
Cowrie
Dev @ Bswen

I spent weeks trying to integrate both GitHub CLI and GitHub MCP for my AI agent setup. The result? CLI won hands down. And I’m not alone.

The Reddit Reality Check

On r/codex, the community was brutal: “CLI is all you need? Do we really need MCPs?” One user summed it up perfectly:

“I have both gh CLI and GitHub MCP, CLI works better. With MCP it is all prompt engineering but CLI usage is in training data.”

The response was overwhelming:

“Anything that has a CLI is WAY better than using an MCP imo… everyone has converged on separately”

“CLI is all you need. Also much easier to test and distribute”

“AI models are always much better at using CLI”

What’s the Real Difference?

CLI: Direct, Predictable, Familiar

CLI tools are the command-line interfaces we’ve used for decades: git, gh, AWS CLI, GCP CLI. They’re direct, programmatic access to functionality through the terminal.

Terminal window
# Immediate, predictable, battle-tested
gh pr create --title "Fix authentication bug" --body "Description here"
aws s3 sync . s3://my-bucket/
gcloud compute instances create web-server --zone=us-central1-a

MCP: Context-Rich but Complex

Model Context Protocol (MCP) is a newer approach that standardizes how applications provide context to LLMs. It uses a client-server architecture:

{
  "mcpServers": {
    "github": {
      "type": "http",
      "url": "https://api.githubcopilot.com/mcp/"
    }
  }
}

Why CLI Wins Every Time

1. Training Data Advantage

Here’s the killer insight: CLI tools are in LLM training data. When an AI model encounters git commit or gh pr create, it knows exactly what to do. MCP servers? They’re all prompt engineering.

I got frustrated constantly having to:

  • Engineer prompts for MCP servers
  • Handle authentication in context
  • Debug abstracted interactions
  • Wait for protocol overhead

2. Performance and Reliability

CLI tools are:

  • Immediate: Direct API calls without abstraction layers
  • Predictable: Standard command patterns across tools
  • Scriptable: Easy to automate and chain commands
  • Universal: No additional server setup required

The community was clear: “10/10 go to the CLI anytime you can… GH, GCP admin, Salesforce”

When MCP Actually Makes Sense

Don’t write off MCP completely. It excels in specific scenarios:

1. Custom Tool Development

When building new AI-accessible tools that don’t have CLI equivalents.

2. Complex Multi-Step Workflows

Coordinating several tools with rich context transfer.

3. Cross-Application Integration

When you need consistent interfaces across diverse tools.

4. Innovation

Exploring new AI interaction patterns for custom systems.

The Hybrid Strategy

Here’s what I recommend:

  1. Start with CLI: Use existing CLI tools whenever possible
  2. Add MCP strategically: Only when necessary for context or custom tools
  3. Let AI leverage CLI: Models are better at using direct interfaces
  4. Watch MCP evolution: The standard may improve over time

Real-World Examples

GitHub Operations

Terminal window
# CLI approach - immediate and direct
gh issue create --title "Bug in auth" --body "Users can't login"
gh pr list --state open --limit 5

Cloud Infrastructure

Terminal window
# Direct, fast, reliable
aws ec2 describe-instances --filters "Name=tag:Environment,Values=prod"
gcloud storage ls gs://my-bucket/*

The Bottom Line

After implementing both approaches, I can tell you: CLI is the clear winner for established tools. The Reddit community got it right - CLI is all you need when it exists.

MCP adds unnecessary complexity for most use cases. The overhead of prompt engineering and protocol management isn’t worth it when you have direct, reliable CLI access.

The key insight: AI models are “always much better at using CLI” because they’ve been trained on these interfaces. MCP requires building new mental models and context handling.

Final Words

For AI agents, CLI tools provide immediate, reliable access to functionality with minimal overhead. They’re battle-tested, universally understood, and performant. While MCP offers interesting context integration capabilities, the complexity and prompt engineering overhead make it less practical for most use cases.

Recommendation: Use CLI whenever possible. Reserve MCP for custom tool development and complex multi-agent systems where rich context transfer is essential.

The community wisdom is clear: CLI is all you need - especially when it already exists.

Final Words + More Resources

My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me

Here are also the most important links from this article along with some further resources that will help you in this scope:

Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!

Comments

Tags: