GitHub MCP exposes the GitHub REST and GraphQL APIs as tools the model can call. It can read code, search across repos, create branches, push commits, manage issues, and open pull requests. Requires a personal access token with the right scopes.

Read repos, manage issues, open PRs from inside Claude or Cursor.

Use Case

Asking Claude to find every TODO across all your repos,Generating a PR that fixes a bug, with a descriptive title and body, in one step,Triaging issues into labels based on natural-language categories,Cross-repo refactors that touch a private monorepo and a public SDK

When Not to Use

Self-hosted Gitea or GitLab (use the dedicated server for those),When you only need read access — the filesystem server + git CLI is faster locally,CI/CD operations — use a workflow runner directly, not the model

Common Pitfalls

  • Token with too-wide scopes — fine-grained PAT scoped to specific repos is safer
  • Rate limits hit fast on big monorepos; cache or narrow your queries
  • GraphQL pagination errors silently — verify expected counts on big result sets
  • Don't commit the token to claude_desktop_config.json if you sync the file