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

July 26, 2026
Thinkode AI
5 min read
ThinkReviewMCPCursorClaude CodeGitHub CopilotCode ReviewProduct

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

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:

  1. You are pairing with an AI agent on a fix or feature branch.
  2. A teammate shares a PR link in Slack or a ticket.
  3. You ask: “Call review_url_code for https://github.com/org/repo/pull/42.”
  4. 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:

  1. Configure git integrations in the portal
  2. Copy your MCP token and client config
  3. 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.

Ship faster with reviews where you already work—in the PR tab or right inside your AI assistant.