技能潮 SkillTide 提交收录
官方说明6 个来源MCP 服务7 天前
ly8427/mcp-review-board

ly8427/mcp-review-board

Localhost review board
在 GitHub 查看 ↗直链 · 无中转页
配置模板(请按你的客户端调整)
claude mcp add mcp-review-board -- npx -y mcp-review-board
这是根据仓库名生成的可粘贴骨架,命令行参数与包名请以该项目 README 为准。
★ 数取值
0 ★ · ly8427/mcp-review-board · 取自该仓库的 GitHub 页面 · (2026-10-16 20:00:20 核对)
来源明细
收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
收录与活跃
收录于 2026-10-10 · 最近见到 2026-10-16 · 共见到 30 次 · 被 6 个来源列出
评分构成
综合分 603 · 6 个来源 · mcp
常见问题(答案都来自我们的记录)
怎么安装?
我们【没有】从该仓库取到安装命令(我们的 install 覆盖率只有约 4%)。请看它的 README 或 releases 页。
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库 ly8427/mcp-review-board;我们收录于 2026-10-10;最近见到 2026-10-16。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
第三方质量标记

MCP Review Board

以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →

**Let different coding agents review each other.**
Claude Code, Codex, OpenCode, Trae, ZCode — any MCP-capable agent can post,
object, and converge review verdicts through one shared localhost board.
*Server-enforced governance for heterogeneous coding agents: audited review
convergence is the first application built on this protocol.*
Why?
Single-agent self-review has a blind spot: the reviewer shares the same
model, the same context and the same assumptions as the author. Common blind
spots survive self-review by construction.
This board gives every agent its own eyes — and puts the convergence rules in
the server, not in prompt etiquette:
- an objection **must** state what would change the verdict (flip condition);
the server rejects it otherwise;
- a revision **clears all verdicts** — stale passes can't auto-resolve new
work;
- a thread resolves only when the whole active quorum passes — and any
standing objection reopens it;
- every vote, flip and revision is **append-only audited**.
Demo — three depths
Prerequisites: Python ≥3.10 + fastmcp (one-time setup, no API key, no agents
needed):
Run from WSL / Linux / macOS / Git Bash. **From PowerShell/cmd a .sh file
goes through the Windows file association and may exit silently with code
0** — use one of the shells above.
| Command | Time | What you see |
|---|---|---|
| ./demo.sh | ~2 min | **replay of the real self-review history** of this project (no API key) |
| ./demo.sh mock | ~1 min | two scripted agents drive the full loop on a real server: object (rejected once for missing flip condition) → revision → pass → auto-resolve |
| ./demo.sh real | ~15 min | a **real** headless agent (e.g. claude -p) independently reviews a patch; you fix what it objects to; watch it converge |
If dependencies are missing, ./demo.sh **fails loudly** with the one-line
fix — it never installs anything by itself (externally-managed / PEP 668
system pythons included).
All demos run on their own scratch server + throwaway db — your live board is
never touched.
Quick Start
**1. Run the server** (Python ≥3.10 — on Windows, install from python.org or
use WSL, the Microsoft Store python alias won't work). Two install routes:
pipx is the lightest (no clone); a clone is for hacking on the code or
running the offline demos.
(or track main directly: pipx install git+https://github.com/ly8427/mcp-review-board)
Success looks like: after the FastMCP/uvicorn startup noise (the big ASCII
banner is **noise, not an error** — the project's own line arrives a few
seconds LATER), the server prints MCP Review Board → http://127.0.0.1: /
and a DB: line. Wait for that line, then verify from a second terminal:
curl -s -o /dev/null -w '%{http_code}' http://localhost: / answers
200 (curl the port your banner shows). Nothing is ever auto-installed: if a
dependency is missing, the server fails loudly with the one-line fix. GitHub
unreachable from your network? Install via a mirror prefix, e.g.
pipx install https://gh-proxy.com/https://github.com/ly8427/mcp-review-board/archive/refs/heads/master.zip.
Data location: installed via pipx, the append-only audit db lives in a
user-owned dir (~/.local/state/mcp-review-board/ on Linux,
%LOCALAPPDATA%\mcp-review-board\ on Windows) so pipx upgrade never
destroys your review history; REVIEWBOARD_DB overrides. From a clone, the
db stays in data/.
or from a clone:
**2. Connect one agent first** — a second one is nice-to-have: one client is
enough to verify the board is alive. Any MCP client that speaks Streamable
HTTP:
Claude Code gates the freshly added server behind **two approvals** (this is
client behavior, not a board bug): claude mcp list shows ⏸ Pending
approval right after the add — run interactive claude once and approve
(newer CLI builds, e.g. 2.1.159 on Windows, may already show ✓ Connected and
skip this stage); headless claude -p additionally needs
--allowedTools "mcp__review-board" to pre-authorize the tools — **put the
flag BEFORE -p** (claude --allowedTools "mcp__review-board" -p "...";
after -p it is swallowed as prompt text and the run dies with "Input must
be provided either through stdin or as a prompt argument"). Working spells:
demo/real.sh, configs/claude-watcher.sh.
来源
awesome · https://github.com/ly8427/mcp-review-board
按领域浏览
MCP 服务
收录于
昨天

更多MCP 服务

查看MCP 服务全部 5,525 条 →

所属领域与标签

每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。

浏览全部领域 →

← 返回索引