claude mcp add mcp-review-board -- npx -y mcp-review-board
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
0 ★ · ly8427/mcp-review-board · read from the repository page · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-10 · last seen 2026-10-16 · seen 30× · listed by 6 sources
Score
score 603 · 6 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository ly8427/mcp-review-board;first catalogued 2026-10-10;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
**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.