GitHub Enterprise Server PR ThinkReview: Finally, A Simple Solution

GitHub Enterprise Server PR ThinkReview: Finally, A Simple Solution

Like many developers working on GitHub Enterprise Server, I've spent years watching AI code review happen on github.com while our internal PRs stayed on Overview, Files changed, and a comment box.

I tried the stack that promised to close that gap. A few tools were useful. All of them shared the same tax: GitHub Apps that never install on GHES, webhooks that need a public callback, org tokens pasted into a SaaS dashboard, and a review that is never the pull request I am actually looking at.

I kept asking: "Why isn't there a simple github enterprise server pr ai review that just works on the PR?"

So I built one.

ThinkReview started on GitLab. GitHub.com came next. GitHub Enterprise Server (GHES) is the instance Copilot still treats as an afterthought. This ghes ai code review lives in the browser on your custom domain — github.mycompany.com, not only github.com. No marketplace app. No bot account. No second tab.

What you get today is a real review panel (severity, scores, agents, follow-up questions), Cloud reviews with full repo context, and ThinkReview MCP so the same GHES pull request URL can be reviewed from Cursor, Claude Code, or Copilot.

Why GHES still needs a simpler PR AI review

If you live on github.com, you have Copilot and a crowded extension ecosystem. If you live on GitHub Enterprise Server, the PR page is still mostly Files changed and a comment box — plus a security policy that will not let you stand up a public webhook.

A github enterprise copilot pr review should not mean:

• Installing a GitHub App that your GHES admin will not approve
• Exposing the instance so a vendor can POST review comments
• Generating an org-wide token you then paste into a dashboard you never open during review
• Copying the diff into ChatGPT and losing the Files tab

ThinkReview is the other path: install the extension, add your GHES domain in settings, open the PR, click AI Review. The review stays on the page.

A custom domain is the one setup step GHES requires so the extension can run on your instance. That is it. No webhooks, no GitHub App, no waiting on an org admin for a marketplace install.

What the extension actually shows now

The github enterprise server pr ai review you get today is a full sidebar on the PR:

• Summary of what the change actually does
• Severity-ranked findings (critical / high / medium) with file and line ranges
• Quality, security, and best-practice scores when you run a scoring review
• Review agents (for example a security or pentest checklist) on the same PR
• Suggested follow-up questions you can click into chat, plus “generate a comment I can post”
• Code suggestions you copy and post yourself — ThinkReview is a copilot, not a comment bot
• Cursor / Claude Code / Copilot deeplinks to implement a finding in the IDE

Cloud reviews can use full repository context on the first pass and search grounding when a finding depends on live docs (model IDs, CVEs, SDK names). You still pick the model in portal model selection.

Same extension, same panel, on GitHub.com, GitHub Enterprise Server, GitLab, Azure DevOps, and Bitbucket. Open the popup, pick GitHub Enterprise Server, add the domain, and you are in the right setup.

Review the same GHES PR from MCP

The extension is for when you are already on the PR. ThinkReview MCP is for when you are in the editor.

Paste a GitHub Enterprise Server pull request URL into Cursor, Claude Code, Claude Desktop, or GitHub Copilot and call review_url_code. ThinkReview fetches the diff through your portal git credentials and returns the same structured review: summary, findings, security notes, scores, follow-up questions.

Hosted endpoint: https://mcp.thinkreview.dev/v1
Listed on the Official MCP Registry as io.github.Thinkode/thinkreview.

Typical Cursor config (OAuth — URL only):

{
  "mcpServers": {
    "thinkreview": {
      "url": "https://mcp.thinkreview.dev/v1"
    }
  }
}

Then Authenticate in the client, finish consent on the ThinkReview portal, and keep GitHub credentials under Settings → Integrations. MCP cannot fetch a private GHES PR without that.

Setup details: ThinkReview MCP · MCP integration docs · MCP setup in the portal

Reviews from MCP use the same credits as the extension. Cached results reuse when the changed-file fingerprint has not changed.

Getting started (still short)

On the GitHub Enterprise Server PR page

1. Install ThinkReview (Chrome / Edge / Firefox)
2. Open the extension popup and choose GitHub Enterprise Server
3. Add your GHES domain (for example github.mycompany.com) and allow the permission (GHES setup)
4. Open any pull request on your instance (/org/repo/pull/123)
5. Click AI Review — the sidebar is the review

From Cursor or Claude Code

1. Connect git credentials in the portal
2. Add ThinkReview MCP and authenticate
3. Ask: Review this GitHub Enterprise Server PR with ThinkReview: https://github.mycompany.com/{owner}/{repo}/pull/{id}

No webhooks. No YAML. No waiting on a GHES admin for a GitHub App.

Built for GitHub Enterprise Server teams

ThinkReview works across:

• github.com (ready as soon as you install)
• GitHub Enterprise Server / on-premises (custom domain setup)
• Public and private repos

There is a free tier (daily review credits) so you can try a real github enterprise server pr ai code review before anyone files a purchase order. Paid plans raise daily credits, agent runs, and giant-PR limits. Custom GHES domains are on paid plans.

ThinkReview stays a copilot: you read the findings, you post the comments. That is why teams who do not want a noisy review bot on an internal instance still use it.

Try the simple github enterprise copilot pr review

I built this because the existing ghes ai code review options were either missing or built only for github.com. The Azure DevOps launch proved the simpler model works on enterprise hosts. GitHub Enterprise Server is the same idea: the review belongs on the PR you already have open.

Install ThinkReview and run it on the next GHES pull request — or paste that PR URL into an assistant with ThinkReview MCP.

Available on Chrome, Edge, Firefox, Opera, Brave, and other Chromium browsers.

What's your biggest pain point with GitHub Enterprise Server Pull Request reviews? Tell us — we keep shipping against that list.

Related:

• Azure DevOps PR ThinkReview: Finally, A Simple Solution
• Bitbucket PR ThinkReview: Finally, A Simple Solution
• GitLab Self-Hosted MR ThinkReview: Finally, A Simple Solution
• ThinkReview now supports GitHub
• Introducing ThinkReview MCP
• ThinkReview MCP is now on the Official MCP Registry