Compare
Lightweight by default. Focused by design.
Both servers talk to the same GitHub API. The difference is what they load into an agent's context and what you have to configure. GitHub Pro MCP starts with 19 read-only tools and exposes 34 when writes are enabled. The official server starts at 46 tools and reaches 91 with every toolset.
Default tools
19
Read-only. Write tools are not registered.
Tool context
~4.1k
Tokens of tool schemas by default.
With writes enabled
34
Opt in with GITHUB_MCP_ENABLE_WRITES=true.
Tool surface and context
| GitHub Pro MCP | Official GitHub MCP | |
|---|---|---|
| Default tools | 19 (read-only) | 46 |
| Full tool set | 34 (GITHUB_MCP_ENABLE_WRITES=true) |
91 (all toolsets) |
| Read-only mode | Default, 19 tools | Optional, 57 tools with all toolsets |
| Tool schema context | ~4.1k tokens default, ~8.0k full | ~31.6k tokens default, ~64.9k all |
| Configuration | None; one fixed surface | Toolsets and individual tools |
| Distribution | npm, one bundle, zero runtime dependencies | Go binary, Docker image, hosted HTTP endpoint |
| Transport | stdio | stdio and remote HTTP |
| Auth | Personal access token | OAuth, PAT or GitHub App |
| License | Proprietary, free to install and use | MIT |
Measured 7 November 2026 against official image v2.1.0. Approximate tokens are serialized
tool definitions divided by four. The official server can be narrowed with
GITHUB_TOOLSETS or --tools; these rows show its default and
all-toolsets configurations.
The daily path
Coverage is a catalog metric. The daily workflow is smaller.
Most agent sessions do not need every GitHub surface. They read an issue, add a comment, open a pull request, change a file, set Priority or Effort, or list repositories in an organization. Those operations repeat every day. Actions, security alerts, notifications, discussions, gists and Copilot matter, but they are not the common path.
GitHub Pro MCP keeps that path in front of the model: 19 tools by default, 34 when writes are enabled. Less context spent on tool definitions, a smaller surface to choose from, and no toolset configuration to maintain. When the long tail is the task, the official server is the better fit.
Domain coverage
Counts are tools per area, not a claim that every tool is equivalent. Official counts use all toolsets.
| Domain | GitHub Pro MCP | Official GitHub MCP | Notes |
|---|---|---|---|
| Issues and issue fields | 14 | 9 | Ours includes first-class issue-field writes. |
| Pull requests | 3 | 10 | Official adds reviews, threads and branch updates. |
| Repositories, files and Git | 8 | 23 | Official adds releases, branches, tags, commits and repository management. |
| Projects v2 | 3 | 3 | Read and write parity. |
| Labels | 2 | 3 | Official adds a single-label lookup. |
| Organizations and context | 4 | 6 | Official adds teams and user search. |
| Actions | - | 4 | Workflows, runs, jobs, logs and triggers. |
| Security and Dependabot | - | 10 | Code scanning, secret scanning, Dependabot and advisories. |
| Code quality | - | 1 | Code quality findings. |
| Notifications | - | 6 | List, dismiss and manage subscriptions. |
| Discussions | - | 5 | Read and write discussions. |
| Gists | - | 4 | List, read, create and update. |
| Governance | - | 4 | Rulesets and custom properties. |
| Copilot | - | 3 | Assign issues and request reviews. |
| Total | 34 | 91 |
Where GitHub Pro MCP wins
- 19 tools and about 3.7k tokens by default, with no toolsets to configure.
- One npm package, one bundle, no runtime dependencies.
- First-class issue-field writes: Priority, Effort and dates.
- A token generator that builds a pre-filled fine-grained PAT with read-only and read-write presets.
- Owner/repo pinning, retries and a circuit breaker.
- Local-only stdio process; use your own token and GHES host.
Where the official server wins
- 91 tools across Actions, security, notifications, discussions, gists, governance and Copilot.
- Hosted remote server with OAuth and a one-click install path.
- Toolset and individual-tool selection.
- MIT license and structured tool output.
- Teams, releases, branches, commits and repository management.
What we deliberately leave out
We do not bundle Actions, security scanning, Dependabot, advisories, notifications, discussions, gists, governance or Copilot tools. If those are your priority, use the official GitHub MCP server. GitHub Pro MCP is for the core issue, pull request, file, project and label workflow, with a small context footprint.