ThinkReview

io.github.Thinkode由 GitHub 帳號 Thinkode 發布v1.3.0更新於 Oct 24, 2026

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

發布方自己的服務:Review Expert

已驗證Streamable HTTP可網頁執行開發者工具AI 與機器學習

概覽

AI 產生的概覽

託管式 MCP 伺服器,讓助理針對 GitHub、GitLab、Azure DevOps 或 Bitbucket 的拉取/合併請求網址執行 AI 程式碼審查。

可以做什麼
針對拉取請求或合併請求網址執行即時程式碼審查,可指定回應語言、追蹤 ID 並略過快取,回傳包含摘要、建議、安全性提醒、最佳實務與後續問題的結構化審查結果。
適用情境
適合希望不必把 diff 貼進對話就能取得結構化 PR/MR 審查的情境,可在支援 Streamable HTTP 的 Cursor、Claude Code、Claude Desktop 或 GitHub Copilot 等用戶端使用。
執行需求
遠端端點 Streamable HTTP。需要具備有效方案或審查額度的 ThinkReview 帳號,並在入口網站的「設定 → 整合」中為 PR 所在主機儲存 git 憑證。驗證方式為 OAuth(建議)或在 Authorization 標頭提供入口網站 Bearer 權杖。若以 Claude Desktop 設定檔方式使用,需 Node.js 執行 mcp-remote 橋接。
安裝前請注意
審查會消耗與 ThinkReview 瀏覽器擴充功能相同的審查額度,因此使用會產生費用。Bearer 權杖是與擴充功能共用的長期入口網站權杖,應避免提交到 git 或寫入設定檔,優先使用 OAuth,外洩後應重新產生。變更檔案會透過你儲存的 git 憑證取得,因此 PAT 只應授予讀取 PR/MR 與 diff 所需的最小權限。重新產生 Bearer 權杖不會撤銷 OAuth 工作階段。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 ThinkReview,將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.Thinkode%2Fthinkreview/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

{
  "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.

來源:README.md,提交 64c1ade

工具

0
該伺服器需要登入,因此 SourceWeft 無法在沒有帳號的情況下讀取其工具,也未收錄。已連接帳號所能看到的內容可能因帳號及其權限而異。

版本歷史

1
  1. v1.3.0最新Sep 16, 2026

評分

已滿足適用檢查項的 85%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Review 整合