ThinkReview MCP
Hosted MCP server that enables AI code reviews on GitHub, GitLab, Azure DevOps, and Bitbucket PR/MR URLs via a single tool (review_url_code), integrating with Cursor, Claude Code, Claude Desktop, and GitHub Copilot through OAuth or Bearer token authentication.
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.
| 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.
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.
| 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.
Authentication
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.
Prerequisites
- A ThinkReview account with an active plan or available review credits
- Git credentials under Settings → Integrations for the host of the PR you want to review
- An MCP client that supports Streamable HTTP, plus either:
- OAuth for remote HTTP servers, or
- A Bearer token from portal.thinkreview.dev/mcp
Quick start — OAuth (recommended)
Add a URL-only config, then Authenticate in your client (browser opens the ThinkReview portal).
Cursor
{
"mcpServers": {
"thinkreview": {
"url": "https://mcp.thinkreview.dev/v1"
}
}
}
Enable thinkreview, click Authenticate, complete portal consent.
Example: examples/oauth/cursor.mcp.json
Claude Code
CLI:
claude mcp add --transport http thinkreview https://mcp.thinkreview.dev/v1

Or config (~/.claude.json / project .mcp.json):
{
"mcpServers": {
"thinkreview": {
"type": "http",
"url": "https://mcp.thinkreview.dev/v1"
}
}
}
Example: examples/oauth/claude.mcp.json
Authenticate (OAuth)
- Start Claude Code and run
/mcp.

- Select thinkreview — status shows needs authentication.

- Choose Authenticate.

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


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

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


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:
{
"mcpServers": {
"thinkreview": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.thinkreview.dev/v1"]
}
}
}

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
GitHub Copilot (VS Code)
.vscode/mcp.json or user MCP config (servers key):
{
"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_codefor 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
{
"mcpServers": {
"thinkreview": {
"url": "https://mcp.thinkreview.dev/v1",
"headers": {
"Authorization": "Bearer <your-token>"
}
}
}
}
Example: examples/bearer/cursor.mcp.json
Claude Code
claude mcp add --transport http thinkreview https://mcp.thinkreview.dev/v1 \
--header "Authorization: Bearer <your-token>"
{
"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)
{
"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)
{
"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.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。