The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the ThinkReview listing page.
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.
| Endpoint | https://mcp.thinkreview.dev/v1 |
| Transport | Streamable HTTP |
| Auth | OAuth (recommended) or Bearer token |
| Registry | io.github.Thinkode/thinkreview |
| Product | thinkreview.dev/features/mcp |
| Docs | thinkreview.dev/docs/mcp-integration |
| Setup | portal.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.
ThinkReview MCP exposes one tool:
review_url_codeRun 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.
| Parameter | Required | Description |
|---|---|---|
prUrl | Yes | Full or domain-style PR/MR URL (e.g. https://github.com/org/repo/pull/42) |
language | No | Response language (default: English) |
mrId | No | Optional tracking ID for your workflow |
forceRegenerate | No | true to bypass cache and force a new review |
URL reviews use the same review credits as the ThinkReview browser extension.
Choose one method. Interactive configs for both are on portal.thinkreview.dev/mcp.
| Method | How it works | Best for |
|---|---|---|
| OAuth (recommended) | URL-only MCP config → Authenticate in the browser on the ThinkReview portal | Cursor, Claude Code, Claude Desktop, Copilot |
| Bearer token | Long-lived portal token in Authorization: Bearer <token> headers | Extension, 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.
Add a URL-only config, then Authenticate in your client (browser opens the ThinkReview portal).
Enable thinkreview, click Authenticate, complete portal consent.
Example: examples/oauth/cursor.mcp.json
CLI:

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


/authorize → portal consent).


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


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:

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

Example: examples/oauth/claude-desktop.mcp.json
.vscode/mcp.json or user MCP config (servers key):
Use Auth / Authenticate on the thinkreview server, then enable it in Copilot Chat.
Example: examples/oauth/vscode-copilot.mcp.json
Call
review_url_codefor https://github.com/org/repo/pull/123
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.
Example: examples/bearer/cursor.mcp.json
Example: examples/bearer/claude.mcp.json
mcp-remote + header)Example: examples/bearer/claude-desktop.mcp.json
Example: examples/bearer/vscode-copilot.mcp.json
Same hosts as the ThinkReview extension:
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.