GitHub MCP servers, compared
A GitHub MCP server is the agent's hands on your repositories, so the comparison is about what it can touch and how that is limited. GitHub's own server covers the API broadly with toolsets you can switch off; smaller servers cover one job, such as issue triage or reading repository contents, with a narrower token. Hosting matters too: a remote server needs no install but sends every call through the host, a local binary keeps the token on your machine. This page compares the servers MCP Toplist has checked for this task.
How the 8 servers below were chosen
- The server's documented purpose is working with GitHub (or a direct alternative for another forge, labelled as such).
- It has a public repository or published documentation that states its tools, token scopes and hosting.
- MCP Toplist has read that documentation and written a profile with sources and a check date.
- Ordered by the composite ranking, which measures popularity and activity, not quality — read the cells, not the order.
Cells say what each server's own documentation says; “Not documented” means the docs are silent, not that the feature is absent. Profiles were checked between Oct 8, 2026 and Oct 8, 2026; ranks are as of across 144,396 active servers.
| Server | Operations | Permission scoping | Authentication | Hosting | Platforms | Requirements |
|---|---|---|---|---|---|---|
| gitlab-mcp #12zereightNo credentials | GitLab: MRs, issues, pipelines, files, wiki, releases, GraphQL | readonly/modify/full modes, toolsets, tool allow/deny lists | PAT, local OAuth2, MCP OAuth proxy, per-caller tokens | Local npx/Docker; self-host remote via Streamable HTTP | GitLab.com and self-hosted GitLab (not GitHub) | Node.js 18.17+ or Docker; GitLab token; some tools need Premium/Ultimate |
| Repomix #39yamadashyNo credentials | Pack and read repository contents, local or GitHub remote | Sandbox mode confines file tools; Secretlint strips credentials | None documented | Local via npx or Docker | Local directories and GitHub URLs | Node.js or Docker; no account |
| GitHub MCP Server #176githubNo credentials | Issues, PRs, code search, Actions, files, security alerts, writes | Toolsets, --tools allowlist, --read-only, lockdown mode | OAuth (remote) or personal access token | Remote at api.githubcopilot.com/mcp/, Docker, or Go binary | GitHub.com, ghe.com; GHES via local server only | GitHub account; Docker or Go for local; PAT scopes repo+ |
| mcp-gitwand #198devlintNo credentials | Local merge-conflict inspection and resolution only | Policy via .gitwandrc; preview tool is a dry run | None documented | Local via npx | Any local Git repository; no forge API | Node.js; a repository with conflicts |
| Octocode #420muvonNo credentials | Local code search: semantic, structural, GraphRAG, commit history | Not documented | None for the server; optional embedding/LLM API keys | Local Rust binary | Any local git checkout; no forge API | Rust binary; optional Voyage/OpenRouter keys; language server for LSP |
| GitHub MCP Server #1,942modelcontextprotocolAPI key | Files, repos, branches, issues, PRs, search; writes included | Token scope only; no toolsets or read-only flag documented | Personal access token | Local via npx or Docker | GitHub.com; GHES not mentioned | Node.js or Docker; GitHub PAT; archived upstream |
| GitMCP #3,026idosalNo credentials | Read docs and search code of public repositories | Public content only; no token or writes | None | Remote at gitmcp.io; self-hostable | Public GitHub.com repositories and GitHub Pages | No account; Node.js only for mcp-remote clients |
| MCP GitHub Repository Server #39,548loglmhqAPI key | Read-only: list and read files of one repository | Single repo via env vars; token with minimal permissions | Personal access token | Local Node build from source | GitHub.com (api.github.com); GHES not mentioned | Node.js and npm; GitHub PAT |
- Operations
- Issues, pull requests, code search, Actions, repository contents, writes?
- Permission scoping
- Toolsets, read-only mode, scoped tokens?
- Authentication
- OAuth sign-in, personal access token, GitHub App?
- Hosting
- Remote (hosted by the publisher), local binary, Docker?
- Platforms
- GitHub.com only, GitHub Enterprise, other forges?
- Requirements
- Runtime, account, paid plan?
- Giving an agent write access? Start with a read-only mode or a fine-grained token limited to the repositories it needs, then widen.
- On GitHub Enterprise Server or GitLab? Check the platform cell first — several servers are GitHub.com-only.
- Want zero install? The hosted remote with OAuth is the quickest path; the local binary keeps the token off third-party hosts.
- Only need code context, not actions? A repository-reading or packing server is smaller and needs fewer permissions.
Each server in detail
- gitlab-mcp →
A community MCP server for GitLab that lets an agent manage projects, merge requests, issues, pipelines, wiki pages, releases, tags and milestones on GitLab.com or a self-hosted instance.
- Repomix →
Repomix packs a whole repository into one AI-friendly file; in --mcp mode it lets an agent pack a local directory or a GitHub repository and then read or grep the packed output.
- GitHub MCP Server →
GitHub's official MCP server connects an agent to the GitHub API so it can read repositories and code, manage issues and pull requests, inspect code security alerts, monitor Actions workflows and work with discussions and notifications.
- mcp-gitwand →
GitWand's MCP server (@gitwand/mcp) exposes its merge-conflict resolution engine so an agent can inspect, preview and resolve Git merge conflicts in a local repository.
- Octocode →
Octocode is a local-first code intelligence tool that indexes a repository into a map of files, symbols, imports and calls, and exposes semantic, structural and GraphRAG search to an agent through an MCP server.
- GitHub MCP Server →
The original reference GitHub server from the MCP project, giving an agent GitHub API access for file operations, repository management, issues, pull requests and search. Its README states that development has moved to github/github-mcp-server and the code now lives in the servers-archived repository.
- GitMCP →
GitMCP is a free, open-source remote MCP server that turns any public GitHub project into a documentation source, so an assistant can read a project's current docs and search its code without setup.
- MCP GitHub Repository Server →
A small MCP server that lets an assistant browse and read the files of one configured GitHub repository through MCP resources.