If you work on self-hosted GitLab, you've probably spent years watching AI code review happen on gitlab.com while your merge requests on gitlab.mycompany.com stay strictly on Overview, Changes, and a static comment box.
Most tools that promise to close that gap come with a heavy tax: GitLab Premium or Ultimate seats, inbound webhooks, dedicated service accounts, and external dashboards that live entirely outside the merge request you are actually reviewing.
We kept asking: Why isn't there a simple GitLab self-hosted AI code review that just works on the MR — on both Community Edition and Enterprise Edition?
So we built ThinkReview.
The Problem with Self-Hosted GitLab AI
If you live on GitLab Community Edition (CE), there is no GitLab Duo. If you live on GitLab Enterprise Edition (EE) without Premium/Ultimate — or on an air-gapped instance — Duo still requires an AI gateway, version pins, and administrative sign-off.
A self-hosted merge request AI review shouldn't mean:
- Upgrading CE to EE Ultimate just to turn AI on
- Standing up GitLab Duo Self-Hosted and complex AI gateways
- Exposing your private instance so an external vendor can POST bot comments
- Copying giant diffs into ChatGPT and losing the context of your Changes tab
A Simple Solution for CE and EE
ThinkReview takes the opposite path: install the extension, add your custom GitLab domain, open the MR, and click AI Review.
No GitLab admin project. No bot accounts. No second browser tab. The review lives right in your browser on your custom domain, supporting:
- GitLab.com
- GitLab Community Edition (CE)
- GitLab Enterprise Edition (EE) — whether you have Duo or not
A custom domain is the only setup requirement so the extension can safely run on gitlab.company.com.
What You Get in the Review Panel

ThinkReview acts as an intelligent copilot right inside your merge request sidebar:
- Summary of what the code change actually does
- Severity-ranked findings (critical / high / medium) with direct file and line ranges
- Quality, security, and best-practice scores on demand
- Review agents (like security or pentest checklists) running on the same MR
- Suggested follow-up questions to dive deeper into chat, plus copy-ready comment generation
- Code suggestions that you copy and post yourself — keeping you in full control
- Cursor / Claude Code / Copilot deeplinks to jump straight into your IDE to fix findings
Review Self-Hosted MRs Directly from MCP
If you prefer working inside your editor, ThinkReview MCP brings the exact same capability to your favorite AI assistant.
Full instructions : https://thinkreview.dev/blog/2026-08-11-thinkreview-mcp-oauth-claude-code-setup
Simply paste a GitLab merge request URL—whether gitlab.com or your self-hosted CE/EE instance—into Cursor, Claude Code, Claude Desktop, or GitHub Copilot and call review_url_code. ThinkReview fetches the diff securely through your portal git credentials and returns a structured review containing summaries, findings, security notes, and follow-up questions.
Hosted endpoint: https://mcp.thinkreview.dev/v1
Listed on the Official MCP Registry as io.github.Thinkode/thinkreview.
Getting Started in Minutes
On the GitLab Self-Hosted MR page:
- Install ThinkReview on Chrome, Edge, or Firefox.
- Open the extension popup and choose GitLab Self-Managed.
- Add your instance domain (e.g.,
gitlab.mycompany.com) and grant permissions. - Open any merge request on Community Edition or Enterprise Edition and click ThinkReview.
From Cursor or Claude Code:
- Connect your git credentials in the ThinkReview portal.
- Add ThinkReview MCP and authenticate.
- Ask your assistant: "Review this GitLab MR with ThinkReview:
https://gitlab.mycompany.com/..."
There is a free tier with daily review credits so you can test out a real GitLab community edition code review right now. Discover more at thinkreview.dev.





Top comments (0)