ThinkReview MCP: run live PR code reviews from Cursor, Claude Code, and Copilot

Jay Elsheikh — Fri, 07 Aug 2026 10:52:48 +0000

You already use Cursor, Claude Code, or GitHub Copilot to write and refactor code. What if the same assistant could run a real ThinkReview analysis on a pull request—without you copying diffs into chat?

Today we are introducing ThinkReview MCP: a hosted Model Context Protocol server at mcp.thinkreview.dev/v1. Connect it once, then ask your assistant to review any PR or merge request URL on GitHub, GitLab, Azure DevOps, or Bitbucket. ThinkReview fetches the changed files, runs the review, and returns structured feedback: summary, suggestions, security notes, best practices, and suggested follow-up questions.

Why MCP for code review?

Browser extensions are great when you are already on a PR page. MCP is for the moments when you are in the editor or terminal and want review context without context-switching.

Typical flow:

You are pairing with an AI agent on a fix or feature branch.
A teammate shares a PR link in Slack or a ticket.
You ask: “Call review_url_code for https://github.com/org/repo/pull/42.”
ThinkReview returns the same quality of review you would get from the extension—grounded in the actual diff, not a guess from partial snippets.

One tool, one URL, no patch upload. That is the whole idea.

What you need before connecting

ThinkReview MCP is designed to be quick to set up, but two things must be in place:

1. Your ThinkReview Bearer token

Generate or copy your personal token from the MCP integration page in the ThinkReview portal. It is the same authorization token used by the ThinkReview browser extension. Add it to your MCP client as:

Authorization: Bearer <your-token>

If you regenerate the token, update every MCP client (and expect the extension to need the new token too).

2. Git credentials in the portal (required)

MCP cannot fetch a PR diff without git access. Before your first review, add a Personal Access Token under Settings → Integrations in the portal.

ThinkReview uses that PAT to call your git host’s API—same as URL-based reviews in the cloud. If integrations are missing, or the token cannot reach a private org repo (for example SSO not authorized on GitHub), reviews will fail with a clear access error instead of a vague API failure.

This step is easy to skip when you are excited to wire up Cursor—but it is the most common reason MCP reviews do not work on the first try.

The `review_url_code` tool

ThinkReview MCP exposes a single tool today:

Tool	What it does
`review_url_code`	Runs a live code review on a PR or MR URL

Required: prUrl — the full pull or merge request link.

Optional: language (response language), mrId (your tracking ID), forceRegenerate (bypass cache when the PR has new commits but you want a fresh review immediately).

Reviews use the same credits as the browser extension. Results are cached per user when the changed-file fingerprint has not changed, so re-asking about the same PR is fast and does not burn credits unnecessarily.

Custom review agents you configure in the portal are not run by default through MCP—the tool returns the main structured review. Agent workflows remain centered in the extension and portal today.

Connect in minutes

The portal MCP setup page includes copy-paste configs for:

Cursor — add thinkreview under mcpServers with the hosted URL and Bearer header
Claude Code — JSON config or a one-line CLI claude mcp add command
GitHub Copilot (VS Code) — .vscode/mcp.json or user MCP config with the servers key

Example for Cursor:

{
  "mcpServers": {
    "thinkreview": {
      "url": "https://mcp.thinkreview.dev/v1",
      "headers": {
        "Authorization": "Bearer <your-token>"
      }
    }
  }
}

Restart your client after saving. Then try a prompt like: “Review this PR with ThinkReview: https://github.com/org/repo/pull/123.”

Full setup details, security notes, and troubleshooting live in our docs: MCP Integration.

Smarter caching and clearer errors

This release ships alongside improvements to the URL review pipeline MCP uses under the hood:

Commit-aware caching — reviews refresh when the PR’s changed-file list changes, not only when you force regeneration
Actionable git errors — private repo or token issues surface as access-denied guidance (check integrations, org access, GitHub SSO) instead of opaque 404s

Try it today

If you already use ThinkReview in the browser, MCP is the natural next step for AI-native workflows:

Configure git integrations in the portal
Copy your MCP token and client config
Ask your assistant to call review_url_code on your next PR

ThinkReview remains open source for the browser extension. Explore the project and install links on thinkreview.dev.

Extension repository: github.com/Thinkode/thinkreview-browser-extension
Chrome Web Store: ThinkReview — AI copilot for pull requests
Firefox Add-ons: ThinkReview on Firefox

Lookin forward to your feedback , any questions would love to hear

original post :

I Built a One-Click Bridge from Azure Devops PRs Code Review Directly to Cursor/Claude Code

Jay Elsheikh — Sat, 18 Apr 2026 00:36:54 +0000

Hi Everyone ,

I’d like to share here a new feature that I implemented in ThinkReview extension workflow which utilises cursor deeplinks with one click to implement critical bugs , best practices or security issues from the code review

ThinkReview is an opensource browser extension that supports Gitlab , Github , Azure Devops and Bitbucket.

In this demo it generates a code review for a Github PR.
I decided to implement one of the best practices it outlined.
I already use cursot , I will click on the cursor button and with one click it will open cursor and implement it

First Go to any PR and select which IDE agent you want to use currently (Cursor , CLaude code and Github copilot are supported but much more to come )

check the code review generated and select one of the points you'd like to implement , here I'm selecting one of the best prctices about moving magic numbers to constants

Once you click the implement via button in my case here I selected cursor , it will open cursor with your prompt ready to be sent

First thing it will check if we are on the correct branch of the PR
otherwise it will stop and ask you to switch to the correct branch manually

here it identified correctly we are not on the correct branch so I'm going to switch to the correct branch manually

Here it implemented the best prctice in the right branch and I was happy to commit and push the code

here I regenerated the review again and I see the best practices scoring has gone up from 90 to 95
Yay

ThinkReview is open source and you can install the extension from Chrome Store and Firefox addons
https://github.com/Thinkode/thinkreview-browser-extension
https://thinkreview.dev

DEV Community: ThinkReview