Azure DevOps PR ThinkReview: Finally, A Simple Solution

Azure DevOps PR ThinkReview: Finally, A Simple Solution
Share

Azure DevOps PR ThinkReview: Finally, A Simple Solution

Updated August 26, 2026 — same URL, current product: extension reviews on the Azure DevOps PR page, plus ThinkReview MCP from Cursor and Claude Code.


Like many developers working with Azure DevOps, I've spent years fighting code review. I tried a stack of AI tools that all promised to make it easier. A few were useful. All of them shared the same tax: tokens, webhooks, service connections, and a dashboard that is never the pull request I am actually reviewing.

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

So I built one.

ThinkReview started on GitLab. Azure DevOps was the next request, and it still is the gap GitHub Copilot does not fill. This azure devops pr ai code review lives in the browser on dev.azure.com and *.visualstudio.com. No marketplace app. No bot account. No second tab.

That is still the point. What changed since this post first ranked is the product around it: a real review panel (severity, scores, agents, follow-up questions), Cloud reviews with full repo context, and ThinkReview MCP so the same Azure DevOps PR URL can be reviewed from Cursor, Claude Code, or Copilot.

ThinkReview AI Review on an Azure DevOps pull request

Why Azure DevOps still needs a simpler PR AI review

If you live in GitHub, you have Copilot and a crowded extension ecosystem. If you live in Azure DevOps, the PR page is still mostly Overview, Files, and a comment box.

An azure devops copilot pr review should not mean:

  • Standing up a service hook and an Azure DevOps app
  • Generating org-wide tokens you then paste into a SaaS dashboard
  • Waiting for a bot to spam the thread
  • Copying the diff into ChatGPT and losing the Files tab

ThinkReview is the other path: install the extension, add a Code (Read) PAT in settings, open the PR, click AI Review. The review stays on the page.

ThinkReview scoring panel on an Azure DevOps pull request

A PAT is the one setup step Azure DevOps requires so we can read the diff. That is it. No webhooks, no service connections, no admin approval for a marketplace extension.

What the extension actually shows now

The original post was a launch note. The azure devops 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

ThinkReview severity layout on an Azure DevOps pull request — Critical and High findings

Suggested follow-up questions in the ThinkReview review panel

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, GitLab, Azure DevOps, and Bitbucket — including Azure DevOps Server / on-prem with a custom domain. Open the popup, pick Azure DevOps Cloud or Azure DevOps Server, and you are in the right setup.

ThinkReview extension Platform Setup — choose Azure DevOps Cloud or Server

Review the same Azure DevOps 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 an Azure DevOps 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 an Azure DevOps PAT under Settings → Integrations. MCP cannot fetch a private PR without that PAT.

ThinkReview MCP calling review_url_code from Claude Code

Structured ThinkReview MCP review result in the assistant

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 Azure DevOps PR page

  1. Install ThinkReview (Chrome / Edge / Firefox)
  2. Open the extension popup and choose Azure DevOps Cloud or Azure DevOps Server
  3. Create an Azure DevOps PAT with Code (Read), save it in the extension, and add a custom domain if you use Azure DevOps Server (Azure DevOps setup)

Azure DevOps extension configuration — save a PAT and add a custom domain

  1. Open any pull request on Azure DevOps Services or Server
  2. 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 Azure DevOps PR with ThinkReview: https://dev.azure.com/{org}/{project}/_git/{repo}/pullrequest/{id}

No webhooks. No YAML. No waiting on an org admin for a marketplace install.

Built for Azure DevOps teams

ThinkReview works across:

  • Azure DevOps Services (dev.azure.com and *.visualstudio.com)
  • Azure DevOps Server / on-premises (custom domain setup)
  • Public and private repos

There is a free tier (daily review credits) so you can try a real azure devops pr ai code review before anyone files a purchase order. Paid plans raise daily credits, agent runs, and giant-PR limits. Azure DevOps Cloud and Server are on Professional.

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

Try the simple azure devops copilot pr review

I built this because the existing azure devops pr ai review options were either missing or over-engineered. The GitLab launch proved the simpler model works. Azure DevOps was next. MCP is the same review, in the tools you already use to write the code.

Install ThinkReview and run it on the next Azure DevOps 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 Azure DevOps Pull Request reviews? Tell us — we keep shipping against that list.


Related: