ThinkReview

io.github.ThinkodePublished by GitHub account Thinkodev1.3.0Updated Oct 24, 2026

Live PR/MR code reviews via review_url_code. OAuth or portal Bearer auth.

The publisher's own server: Review Expert

VerifiedStreamable HTTPWeb executableDeveloper ToolsAI & ML

Overview

AI-generated overview

Hosted MCP server that lets an assistant run an AI code review on a GitHub, GitLab, Azure DevOps or Bitbucket pull/merge request URL.

What you can do
Run a live code review on a pull request or merge request URL, with optional response language, tracking ID and cache bypass, returning a structured review with summary, suggestions, security notes, best practices and follow-up questions.
When to use it
Useful when you want a structured review of a PR/MR without pasting a diff into chat, from clients such as Cursor, Claude Code, Claude Desktop or GitHub Copilot that support Streamable HTTP.
Requirements
Remote endpoint at over Streamable HTTP. A ThinkReview account with an active plan or review credits, and git credentials stored in the portal under Settings, Integrations for the PR host. Authentication is OAuth (recommended) or a portal Bearer token in the Authorization header. Claude Desktop config-file use needs Node.js for the mcp-remote bridge.
Before you install
Reviews consume the same review credits as the ThinkReview browser extension, so usage costs credits. The Bearer token is a long-lived portal token shared with the extension; keep it out of git and config files where possible, prefer OAuth, and regenerate it if exposed. Changed files are fetched through your stored git credentials, so grant PATs only the minimum scopes needed to read PRs/MRs and diffs. Regenerating the Bearer token does not revoke OAuth sessions.

Installation

In SourceWeft

  1. Open ThinkReview in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Thinkode%2Fthinkreview/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "thinkreview": {
      "type": "http",
      "url": "https://mcp.thinkreview.dev/v1"
    }
  }
}

README

ThinkReview MCP

Hosted Model Context Protocol server for AI code reviews on pull request and merge request URLs.

Connect Cursor, Claude Code, Claude Desktop, or GitHub Copilot, paste a PR/MR URL, and get a structured review — without pasting a diff into chat.

Endpointhttps://mcp.thinkreview.dev/v1
TransportStreamable HTTP
AuthOAuth (recommended) or Bearer token
Registryio.github.Thinkode/thinkreview
Productthinkreview.dev/features/mcp
Docsthinkreview.dev/docs/mcp-integration
Setupportal.thinkreview.dev/mcp

This repository is for visibility and client documentation. ThinkReview MCP runs as a remote hosted server. The review engine, auth, billing, and git integrations stay on ThinkReview infrastructure and are not published here.


What it does

ThinkReview MCP exposes one tool:

review_url_code

Run a live code review on a GitHub, GitLab, Azure DevOps, or Bitbucket PR/MR URL.

ThinkReview fetches changed files through your stored git credentials (portal Integrations) and returns a structured review: summary, suggestions, security notes, best practices, and suggested follow-up questions.

ParameterRequiredDescription
prUrlYesFull or domain-style PR/MR URL (e.g. https://github.com/org/repo/pull/42)
languageNoResponse language (default: English)
mrIdNoOptional tracking ID for your workflow
forceRegenerateNotrue to bypass cache and force a new review

URL reviews use the same review credits as the ThinkReview browser extension.


Authentication

Choose one method. Interactive configs for both are on portal.thinkreview.dev/mcp.

MethodHow it worksBest for
OAuth (recommended)URL-only MCP config → Authenticate in the browser on the ThinkReview portalCursor, Claude Code, Claude Desktop, Copilot
Bearer tokenLong-lived portal token in Authorization: Bearer <token> headersExtension, CI, or clients that cannot complete OAuth

OAuth sessions are separate from the extension Bearer token. Regenerating the Bearer token does not revoke OAuth MCP sessions.


Prerequisites

  1. A ThinkReview account with an active plan or available review credits
  2. Git credentials under Settings → Integrations for the host of the PR you want to review
  3. An MCP client that supports Streamable HTTP, plus either:

Quick start — OAuth (recommended)

Add a URL-only config, then Authenticate in your client (browser opens the ThinkReview portal).

Cursor

json
{  "mcpServers": {    "thinkreview": {      "url": "https://mcp.thinkreview.dev/v1"    }  }}

Enable thinkreview, click Authenticate, complete portal consent.
Example: examples/oauth/cursor.mcp.json

Claude Code

CLI:

bash
claude mcp add --transport http thinkreview https://mcp.thinkreview.dev/v1

[Add ThinkReview MCP with Claude Code CLI]

Or config (~/.claude.json / project .mcp.json):

json
{  "mcpServers": {    "thinkreview": {      "type": "http",      "url": "https://mcp.thinkreview.dev/v1"    }  }}

Example: examples/oauth/claude.mcp.json

Authenticate (OAuth)
  1. Start Claude Code and run /mcp.

[Open /mcp in Claude Code]

  1. Select thinkreview — status shows needs authentication.

[thinkreview needs authentication]

  1. Choose Authenticate.

[Select Authenticate]

  1. Claude Code opens the browser OAuth flow (/authorize → portal consent).

[Browser OAuth URL in Claude Code]

[Authorize ThinkReview MCP on the portal]

  1. After you click Allow, return to Claude Code — you should see Authentication successful.

[Authentication successful]

Run a review

Ask Claude Code to review a PR URL (tool: review_url_code):

[Invoke review_url_code]

[Example review result]

Claude Desktop

Preferred: Settings → Connectors → Add custom connector → https://mcp.thinkreview.dev/v1 → Connect → complete portal OAuth.

Claude Desktop’s claude_desktop_config.json does not accept Claude Code’s "type": "http" block. To use the config file instead, bridge with mcp-remote (requires Node.js), then fully quit and reopen Desktop:

json
{  "mcpServers": {    "thinkreview": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://mcp.thinkreview.dev/v1"]    }  }}

[claude_desktop_config.json with mcp-remote]

After restart, Settings → Developer → Local MCP servers should show thinkreview as running. Complete OAuth when prompted (same portal consent as Claude Code).

[thinkreview running in Claude Desktop]

Example: examples/oauth/claude-desktop.mcp.json

GitHub Copilot (VS Code)

.vscode/mcp.json or user MCP config (servers key):

json
{  "servers": {    "thinkreview": {      "type": "http",      "url": "https://mcp.thinkreview.dev/v1"    }  }}

Use Auth / Authenticate on the thinkreview server, then enable it in Copilot Chat.
Example: examples/oauth/vscode-copilot.mcp.json

Example prompt

Call review_url_code for https://github.com/org/repo/pull/123


Alternative — Bearer token

Copy your token from portal.thinkreview.dev/mcp and add it as a header. Same session token as the browser extension. Regenerating invalidates the previous token for extension and Bearer-based MCP clients.

Cursor

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

Example: examples/bearer/cursor.mcp.json

Claude Code

bash
claude mcp add --transport http thinkreview https://mcp.thinkreview.dev/v1 \  --header "Authorization: Bearer <your-token>"
json
{  "mcpServers": {    "thinkreview": {      "type": "http",      "url": "https://mcp.thinkreview.dev/v1",      "headers": {        "Authorization": "Bearer <your-token>"      }    }  }}

Example: examples/bearer/claude.mcp.json

Claude Desktop (mcp-remote + header)

json
{  "mcpServers": {    "thinkreview": {      "command": "npx",      "args": [        "-y",        "mcp-remote",        "https://mcp.thinkreview.dev/v1",        "--header",        "Authorization:${AUTH_HEADER}"      ],      "env": {        "AUTH_HEADER": "Bearer <your-token>"      }    }  }}

Example: examples/bearer/claude-desktop.mcp.json

GitHub Copilot (VS Code)

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

Example: examples/bearer/vscode-copilot.mcp.json


Supported platforms

Same hosts as the ThinkReview extension:

  • GitHub.com and GitHub Enterprise Server
  • GitLab.com and self-managed GitLab
  • Azure DevOps Cloud and on-premise
  • Bitbucket Cloud and Bitbucket Data Center

Security

  • Prefer OAuth so long-lived tokens are not stored in MCP config files
  • If you use a Bearer token, treat it like a password — do not commit it to git
  • Store tokens only in local MCP client config or a secrets manager
  • Regenerate the Bearer token from the portal if it is ever exposed
  • Use git PATs with the minimum scopes needed to read PRs/MRs and diffs

Related


License

Documentation and example configs in this repository are licensed under the MIT License.

The ThinkReview hosted MCP service, APIs, and review infrastructure remain proprietary to Thinkode / ThinkReview.

Source: README.md at commit 64c1ade

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.3.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Review integrations