GitHub’s official MCP server. The fastest way to give Claude Code, Cursor, or Cline read/write access to repositories, issues, pull requests, Actions runs, and Discussions across your personal and organization accounts.
What it produces: structured tool calls that read repo metadata, list/create/update issues and PRs, search code across orgs, and trigger or inspect GitHub Actions workflows. Works against the GitHub REST + GraphQL APIs under the hood.
Best for: solo founders running a one-repo factory, agencies juggling 10+ client repos, and anyone who hates context-switching between Claude Code and the GitHub UI to triage a PR.
Skip if: you only need read-only blame/log on a local checkout — the lighter Git MCP covers that without auth setup.
Setup gotchas: requires a GitHub personal access token (or fine-grained PAT) with the right scopes — repo, workflow, and read:org cover most workflows. Token in ~/.config/claude/mcp.json, never in the repo. Fine-grained tokens limited to specific repos are the safer default for paid orgs.
Real-world workflow: I run it as a permanent MCP in Claude Code. When a CI run fails, I ask “what broke in the last main run on 500k-io?” and it pulls the logs, identifies the failing step, and proposes a fix in one round-trip. Same pattern for code review: paste a PR number, get a structured diff review.
Compatible alternatives: Git MCP for local-only work, GitLab MCP if you’re not on GitHub.
I install this on every project that ships code through GitHub. Non-negotiable.