The GitHub MCP server is powerful, but for most GitHub work I default to the GitHub CLI. It's faster to set up, doesn't require juggling keys, and keeps my AI tools focused on the work instead of spending tokens just to fetch GitHub data.

Why GitHub CLI First

GitHub CLI covers everything I actually do in GitHub day-to-day: repo navigation, issues, PRs, checks, releases, and workflows. It runs locally, plugs into the same terminal flow as git, and doesn't require a separate MCP server.

  • No API keys: gh auth login uses a web OAuth flow and stores credentials in your system credential store
  • No extra token spend: the CLI does the API work without routing through your LLM context
  • Low friction: install once, authenticate once, and it works everywhere

Quick Links

Install + Auth in Two Steps

On macOS, it's as simple as:

brew install gh

# Authenticate via browser OAuth flow
# Follow the prompts to pick GitHub.com or Enterprise
# and set your preferred git protocol
gh auth login

On Windows and Linux, use the official installers from the GitHub CLI page. The CLI handles OAuth in your browser, stores credentials securely, and you can skip creating personal access tokens entirely.

How I Prompt My AI Tools

This is the part most people skip. If you're using an AI assistant, be explicit: tell it to use the GitHub CLI. That way it doesn't reach for APIs, tokens, or MCP setup.

  • "Use GitHub CLI to list my open PRs and show which checks are failing."
  • "Use GitHub CLI to create a draft PR from my current branch."
  • "Use GitHub CLI to list issues assigned to me in this repo."
  • "Use GitHub CLI to view the latest release notes."

Vendor CLI vs MCP

Here's the rule I try to follow with AI tool integrations: if the vendor already ships a first-class CLI, start there. It's usually the most stable, most complete, and lowest-friction option. MCP shines when you need to connect multiple systems or expose data the CLI can't reach. But for single-vendor workflows like GitHub, the CLI is hard to beat.

If your workflow is already in the terminal, GitHub CLI is the shortest path from intent to action.
GitHub GitHub CLI MCP AI Tools Developer Productivity