MCP connector: GitHub
The GitHub MCP connector is a pre-built integration that uses the Model Context Protocol (MCP) to give Claude direct, authenticated access to GitHub repositories and project data. Rather than copying and pasting code or issue text into a chat window, you connect Claude to GitHub once, and it can then read files, list issues, inspect pull requests, view commit history, and—when configured with the right permissions—create branches, commit changes, and open pull requests on your behalf.
MCP (Model Context Protocol) is a standardized protocol Anthropic launched in November 2024 that lets Claude communicate with external services through a consistent interface. The GitHub connector follows this standard, which means the tools Claude uses to query GitHub (list_issues, create_pull_request, read_file, etc.) work the same way whether you set up the connector in the claude.ai web interface or configure a local MCP server in Claude Code or Claude Desktop.
There are two distinct GitHub integrations worth distinguishing. The MCP connector described here is available across Pro, Max, Team, and Enterprise plans and gives Claude tool-based, programmatic access to GitHub. A separate native GitHub integration was released in beta for Enterprise users in October 2025 and syncs repositories more directly into Claude's context. This document covers the MCP connector approach.
When you’d use it
- ◆Codebase onboarding for new engineers — A developer joining a large project asks Claude to read the repository structure, README, and key configuration files, then produce a plain-English setup guide explaining how the pieces fit together.
- ◆Automated pull request review — A team lead connects the GitHub MCP and asks Claude to review the diff of an open pull request, checking for logic errors, security issues, and deviations from the project's coding style guide.
- ◆Issue-driven feature implementation — A developer tells Claude to read a specific GitHub issue, implement the requested change in the relevant files, commit to a new branch, and open a pull request—all without leaving the conversation.
- ◆Cross-repository dependency analysis — An architect asks Claude to compare how two separate repositories handle authentication, identifying inconsistencies that could cause integration problems before a planned merge.
- ◆CI/CD log triage — An engineer asks Claude to fetch the logs from the latest failed GitHub Actions run, identify the root cause, and suggest the specific code change needed to make the build pass.
What changed recently
- ◆2024-11 — Anthropic launched the Model Context Protocol (MCP) publicly, establishing the foundation for all MCP connectors including GitHub. Community adoption was rapid, with thousands of MCP servers built shortly after launch.
- ◆2025-10-31 — Anthropic released a separate native GitHub integration in beta for Enterprise plan users, distinct from the MCP connector. This integration syncs repository context directly and was announced alongside other Enterprise features.
- ◆2025-11 — The MCP client version header was updated from mcp-client-2025-04-04 to mcp-client-2025-11-20. Tool configuration was moved to the tools array as MCPToolset objects, enabling more flexible allowlisting and denylisting of individual MCP tools.
- ◆2026-04 — Anthropic updated support documentation confirming custom connectors using remote MCP are available on Free, Pro, Max, Team, and Enterprise plans. Documentation also clarified best practices for local MCP server configuration, distinguishing local Git CLI operations from remote repository management via MCP.
This is the short version
The full chapter has three worked examples, the common pitfalls, and the workflow that makes it pay — plus the other 84 features, kept current.
Get Claude Master — $97 →