GitHub, GitLab & PR Code Review MCP Servers: 2026 Buyer & Integration Guide
Which code-review MCP server should your agent connect to? A verified comparison of the GitHub, GitLab, Graphite, Greptile and adjacent listings on LightState, with the setup paths that actually work today.
Code-review MCP servers fall into three buckets: platform servers that read and write pull requests (GitHub, GitLab, Gitee, GitKraken), AI reviewer services that expose their review results to your agent (Greptile, Graphite, Ellipsis, Augment Code), and context servers that make reviews smarter (Sentry, Linear, Digma). Start with the official GitHub or GitLab server in read-only mode, then add one reviewer service and one context server. Several catalog install commands in this category are outdated, so this guide lists the vendor-documented setup for each.
Verified Capabilities Benchmarked in This Guide
Inspect Live JSON Feed ↗GitHub Official MCP — Repositories, Pull Requests, Actions & Code Search
Official GitHub MCP server for searching repositories, inspecting PR diffs and review comments, triaging issues, and reading GitHub Actions workflow runs.
GitLab Merge Requests, CI Pipelines & Issue Tracker MCP Server
Connect AI coding agents to GitLab self-hosted or cloud instances: inspect Merge Request diffs, debug failed GitLab CI jobs, and update issues.
Graphite MCP
Create, restack, submit, and merge stacked Git pull requests alongside Diamond AI code reviews via Graphite MCP.
Greptile MCP
Query full-repository semantic graphs, review pull requests with full codebase context, and trace cross-repo dependencies via MCP.
CodeRabbit MCP
Fetch line-by-line AI pull request reviews, architectural summaries, and security findings directly inside your IDE agent.
Sentry Official MCP — Stack-Trace Root-Cause & Seer Issue Triage
Official Sentry MCP server: inspect production exceptions, resolve source-mapped stack traces, query release regression metrics, and invoke Seer root-cause
Linear Official Remote MCP — Issues, Cycles, Triage & Roadmaps
Official Linear Streamable HTTP MCP server: search and create engineering issues, update sprint cycle states, link GitHub PRs, and synthesize project statu
Digma MCP — A code observability MCP enabling dynamic code analysis based on OTE
A code observability MCP enabling dynamic code analysis based on OTEL/APM data to assist in code reviews, issues identification and fix, highlighting risky
1. What a code-review MCP server actually gives your agent
An MCP server turns a code host or review product into typed tools your agent can call over JSON-RPC. For pull request work, the tools that matter are: read the PR (metadata, diff, changed files, commits, CI status), read existing review threads, draft a pending review with line comments, and submit or discard that review. Everything else (merging, pushing branches, editing workflows) is a write capability you should only grant deliberately. When comparing servers, ask three questions: which of those tools exist, how authentication is scoped, and whether you can restrict the server to read-only.
- Read tools: PR details, diff, changed files, commits, combined status, review threads.
- Review tools: create a pending review, add line comments, submit or delete the review.
- High-risk tools: merge, push, branch creation, workflow edits. Keep these off unless you need them.
2. The verified comparison matrix
The table below covers every code-review-related MCP listing in the LightState catalog. The Setup column reflects what we could verify against vendor documentation on 25 Oct 2026, not just what the listing card says.
| Listing | Type | Pulse | Transport & auth (verified) | Setup status |
|---|---|---|---|---|
| GitHub MCP (/mcp/github-mcp) | Platform server | 81 | Remote HTTP at api.githubcopilot.com/mcp/ with OAuth or PAT; or local Docker image ghcr.io/github/github-mcp-server | Use the official github/github-mcp-server paths. The catalog's npm package (@modelcontextprotocol/server-github) is deprecated. |
| GitLab MCP (/mcp/gitlab-mcp) | Platform server | 82 | Built into GitLab: https://<your-gitlab>/api/v4/mcp over HTTP, OAuth with the mcp scope or a fine-grained PAT | Use GitLab's native server (HTTP transport introduced in GitLab 18.6). The catalog's npm package is deprecated. |
| Gitee MCP (/mcp/gitee-mcp) | Platform server | 85 | stdio, Gitee access token | Go project (oschina/mcp-gitee). Build or download per the repo README. |
| GitKraken MCP (/mcp/gitkraken-mcp) | Platform + multi-provider | 84 | stdio via the GitKraken CLI (gk mcp) | Install the gk CLI from gitkraken/gk-cli, then run gk mcp. |
| Graphite MCP (/mcp/graphite-dev-mcp) | Stacked PR workflow | 94 | stdio via the Graphite CLI (gt 1.6.7+), beta | claude mcp add graphite gt mcp (vendor docs). |
| Greptile MCP (/mcp/greptile-mcp) | AI reviewer results | 92 | Remote HTTP at api.greptile.com/mcp, OAuth or org API key | claude mcp add --transport http greptile https://api.greptile.com/mcp (vendor docs). |
| CodeRabbit (/mcp/coderabbit-mcp) | AI reviewer | 92 | CodeRabbit documents itself as an MCP client that consumes your MCP servers during reviews | No public CodeRabbit MCP server package found; treat the listing as an integration target, not an installable server. |
| Ellipsis MCP (/mcp/ellipsis-dev-mcp) | AI reviewer | 93 | Listing endpoint answered our probe with HTTP 401 (auth required) | Listed npm package not found. Confirm setup with the vendor. |
| Augment Code MCP (/mcp/augment-code-mcp) | Codebase context | 96 | Listing endpoint did not respond to our probe | Listed npm package not found. Confirm setup with the vendor. |
| Sentry MCP (/mcp/sentry-mcp) | Context: production errors | 83 | Remote HTTP at mcp.sentry.dev/mcp, OAuth (verified 401 challenge) | claude mcp add --transport http sentry https://mcp.sentry.dev/mcp |
| Linear MCP (/mcp/linear-mcp) | Context: issues & specs | 84 | Remote HTTP at mcp.linear.app/mcp, OAuth (verified 401 challenge) | claude mcp add --transport http linear https://mcp.linear.app/mcp |
| Digma MCP (/mcp/digma-mcp) | Context: runtime/OTEL data | 89 | Digma's README describes observability-assisted code reviews; early-access sign-up | Follow digma-ai/digma-mcp-server README. |
3. How to choose: three buyer profiles
Most teams do not need every server. Pick by where your code lives and what you want the agent to do with a pull request.
- GitHub-hosted team that wants AI review summaries: GitHub MCP (read-only pull_requests toolset) plus Greptile MCP to pull existing AI review comments and apply fixes.
- Self-managed GitLab: GitLab's built-in /api/v4/mcp server with the toolsets header to limit tools, plus Sentry MCP for production context on merge requests.
- Agent that writes large changes: Graphite MCP so the agent submits stacked, reviewable PRs instead of one giant diff, plus GitHub MCP read tools for the reviewer side.
4. Minimal verified setup (GitHub + one reviewer + one context server)
These commands come from each vendor's documentation and were cross-checked on 25 Oct 2026. The GitHub URL below uses the read-only variant of the pull_requests toolset so your first integration cannot write anything.
5. Red flags when evaluating any code-review MCP listing
While verifying this category we found install commands pointing at deprecated or non-existent npm packages, and endpoints that did not respond. Before you install anything, run these checks yourself.
- Does the package exist and is it maintained? Run npm view <package> and look for a deprecation notice.
- Is the source repo owned by the vendor? Official servers live under the vendor's GitHub org (for example github/github-mcp-server).
- Does the remote endpoint answer an MCP initialize request with a proper 401 and a WWW-Authenticate header pointing at OAuth metadata? That is what a healthy protected server looks like.
- Can you restrict it to read-only? GitHub supports /readonly URLs and GITHUB_READ_ONLY=1; GitLab supports a toolsets header.
6. Maintainers: claim and correct your listing
Verification note: LightState checked every install path in this guide on 25 Oct 2026. Where a listing's catalog install command could not be confirmed (npm package not found, deprecated, or endpoint not responding), we say so and point to the vendor's own documented setup instead. Pulse Scores are the LightState catalog values on the same date. If you maintain one of these servers, claim the listing to correct its install command, transport and endpoint so agents stop trying broken paths.
Frequently Asked Questions
What is the best MCP server for GitHub pull request review in 2026?
Start with GitHub's official server (github/github-mcp-server). Its remote endpoint at api.githubcopilot.com/mcp/ exposes pull_request_read (diff, files, commits, status, review threads) and review-writing tools, and every toolset has a /readonly URL variant for safe first installs.
Is there an official GitLab MCP server?
Yes. GitLab ships an MCP server inside GitLab itself at https://<your-gitlab>/api/v4/mcp. HTTP transport was introduced in GitLab 18.6, and it accepts OAuth tokens with the mcp scope or fine-grained personal access tokens.
Should I still use @modelcontextprotocol/server-github or server-gitlab?
No. Both npm packages are marked deprecated on the npm registry. Use the vendor-maintained GitHub server and GitLab's built-in server instead.
Does CodeRabbit have an MCP server?
CodeRabbit's documentation describes it as an MCP client: it connects to your MCP servers (for example Linear, Sentry or GitHub Copilot) to add context to its reviews. We could not find a public CodeRabbit MCP server package.
How do I fix wrong details on a LightState listing?
Claim the listing at /claim with your X handle, then update the install command, transport and endpoint. Unclaimed listings show the catalog values we verified on the date of each guide.