MCP Integration

ThinkReview MCP lets AI coding assistants run live code reviews on pull request or merge request URLs — without pasting a diff into chat. ThinkReview fetches changed files through your stored git credentials and returns a structured review (summary, suggestions, security notes, best practices, and suggested questions).

Hosted endpoint: https://mcp.thinkreview.dev/v1

For interactive setup (copy your Bearer token and ready-made client configs), use the MCP setup page in the ThinkReview portal.

Prerequisites

Before connecting an MCP client, make sure you have:

1. A ThinkReview account with an active plan or available review credits.
2. A Bearer authorization token from portal.thinkreview.dev/mcp. This is the same session token used by the ThinkReview browser extension. Regenerating the token invalidates the previous one everywhere (extension, webapp, and MCP).
3. Git credentials configured in the portal under Settings → Integrations. This is required for MCP URL reviews to work. ThinkReview uses your Personal Access Token (PAT) to call GitHub, GitLab, Bitbucket, or Azure DevOps APIs and fetch the PR/MR diff. Without integrations, reviews will fail with a git credentials or access error.

Supported git hosts match the extension: GitHub, GitLab, Bitbucket, and Azure DevOps (cloud and many self-hosted patterns). See GitHub Integration, GitLab Integration, and related setup docs for PAT scopes.

What the MCP server provides

ThinkReview MCP exposes one tool:

Tool	Purpose
review_url_code	Run a live URL-based code review on a PR or MR URL

Optional parameters:

Parameter	Description
prUrl	Required. Full or domain-style PR/MR URL (e.g. https://github.com/org/repo/pull/42)
language	Response language (default: English)
mrId	Optional tracking ID for your workflow
forceRegenerate	Set to true to bypass cache and force a new review

URL reviews use the same review credits as reviews in the browser extension. Cached results are reused when the PR file list has not changed (see Cached Reviews).

Agent reviews (custom review agents configured in the portal) are not triggered by default through MCP. MCP returns the main code review only.

Cursor setup

1. Open Cursor → Settings → MCP (or edit your MCP config file).
2. Add the ThinkReview server:

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

3. Replace <your-token> with the Bearer token from portal.thinkreview.dev/mcp.
4. Restart Cursor or reload MCP servers.

Example prompt: “Call review_url_code for https://github.com/org/repo/pull/123”

Claude Code setup

Option A — CLI

claude mcp add --transport http thinkreview https://mcp.thinkreview.dev/v1 --header "Authorization: Bearer <your-token>"

Option B — Config file (~/.claude.json or project .mcp.json):

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

Restart Claude Code after saving.

GitHub Copilot (VS Code) setup

1. Run MCP: Open User Configuration or create .vscode/mcp.json in your project.
2. Add:

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

3. Enable the thinkreview server in Copilot Chat and invoke review_url_code from your assistant.

Security best practices

• Treat your Bearer token like a password. Do not commit it to git or share it in public channels.
• Store tokens only in your local MCP client config or a secrets manager.
• Regenerate the token from the portal if it is ever exposed.
• Use git PATs with the minimum scopes needed to read pull requests and file diffs for repositories you review.

Troubleshooting

“Unauthorized” or MCP asks to authenticate

• Confirm Authorization: Bearer <token> is set in your MCP client headers (exact spelling, including Bearer ).
• Copy a fresh token from portal.thinkreview.dev/mcp — an old token fails after regeneration or sign-out.
• Restart your MCP client after updating the config.

Git credentials unavailable / cannot access repository

• Add or update your PAT under portal.thinkreview.dev → Settings → Integrations. MCP cannot review a PR without this step.
• For private organization repos (e.g. GitHub), ensure the PAT has access to the org and SSO is authorized for the token if your organization requires it.
• Verify the PR URL matches the host and repo your credential is configured for.

Review returns cached results

• URL reviews are cached per user when the changed-file fingerprint is unchanged. Pass forceRegenerate: true in review_url_code to request a fresh review.

Still stuck?

Contact support or report a bug with your git host, PR URL (redact secrets), and the error message from your MCP client.

---

TL;DR: Add ThinkReview MCP at https://mcp.thinkreview.dev/v1 with your portal Bearer token, configure git credentials under Integrations, then ask your assistant to call review_url_code with a PR URL.