Log inSubmit server
Review Assist MCP logo

Review Assist MCP

Captures coding-agent intent, validates it against a diff, and presents a guided GitHub pull-request review.

InstallRepository
Full README Compare alternatives Embed widget Claim this listing

Install Review Assist MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "review-assist-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "review-assist-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 23 tools correctly (Today).

Overview

review-assist-mcp turns a coding-agent session into an Intent Document describing the request, assumptions, verification, and diff tour. Its MCP server runs on the developer’s machine, where it helps author and validate the document before it is committed with the code. A GitHub App checks coverage on pull requests and presents an anchored review interface for reviewers. Reach for it when AI-generated changes need their lost context restored without sending the session transcript off the developer’s machine.

Use cases

  • Capture an AI agent’s assumptions alongside its code changes
  • Validate that an Intent Document covers a pull-request diff
  • Guide reviewers through anchored stops in an AI-generated change
  • Add repository-specific verification questions to code reviews

Key features

  • Intent Document authoring through MCP
  • Diff coverage and document validation
  • GitHub pull-request checks and summaries
  • Anchored guided review
  • Repository-specific reviewer guidance
  • Local transcript handling

Tools23

What Review Assist MCP lets your agent do. Expand a tool for its parameters.

Verified live~7.8k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

8/8 checks healthy over the last 55d

What it can do

From the 23 tools this server returned when we ran it; 23 declare their own safety hints.

Runs commands · 1Can delete or modify data · 3Read-only tools · 20
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age98 days
Maintainers1

Observed 2026-11-02 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13h ago via OSV.dev · review-assist-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1.4kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed23Callable tools this server registers over MCP.

How Review Assist MCP works

What review-assist-mcp does

review-assist-mcp captures the reasoning around an AI-written change in an Intent Document. The document records what was requested, which assumptions shaped the implementation, what was tried or rejected, what was verified, and how the diff should be read. It is committed alongside the code so reviewers can examine the change with more context than the final patch alone provides.

The package contains an MCP server for the authoring workflow, along with validation and rendering components in the wider project. A separate GitHub App checks pull requests, posts review status and a summary, and opens a guided review for the repository’s reviewers.

How it works

The MCP server runs on the developer’s machine beside the coding agent. It drives the creation of an Intent Document and controls submission through local checks. The validator checks the document schema, coverage of the change, stale references, cross-references, and likely secrets before the document is written.

After the document reaches GitHub with the code, the GitHub App reads the pull request and document for each request. It recounts whether the document explains the diff and posts the result as a check and pull-request summary. Reviewers can open the guided viewer, read verified points and open assumptions, follow anchored stops through the diff, and classify items as accepted, questions for the author, or blocking. Their verdict and notes are posted to GitHub under the reviewer’s identity.

Repository-specific review guidance can be placed in a committed .reviewer/ directory. Its Markdown files can add questions and explain local verification expectations, while the schema and validation rules remain enforced by code.

Setup and configuration

Install the MCP server separately for each coding-agent configuration you use. Claude Code can register it with claude mcp add, while Codex uses codex mcp add; both examples launch review-assist-mcp through npx -y. Claude Code also has a plugin installation option that packages the server and review agents together.

Claude Desktop can install the published .mcpb package. A VS Code extension shares the Claude Code or Codex configuration, depending on the agent setup. When a macOS GUI application cannot find npx on its restricted PATH, install the package globally and register the server with the Node executable and the package’s dist/index.js path instead.

The GitHub App must also be installed on the repository. It requests read-only code and pull-request comment access and adds the automated check, summary comment, and guided-review viewer. Running the server through npx -y resolves the latest release at launch; global installations can be updated with the package’s @latest tag.

Tools and capabilities

  • Creates Intent Documents from coding-agent sessions.
  • Validates document structure, diff coverage, freshness, cross-references, and likely secrets.
  • Renders Intent Documents as Markdown.
  • Adds GitHub pull-request checks and review summaries through the companion app.
  • Provides anchored guided review with reviewer notes and verdicts.
  • Accepts repository-specific guidance from .reviewer/README.md and .reviewer/verification.md.

Limitations and notes

The MCP server and session transcript stay on the developer’s machine. The GitHub application does not keep a database: it reads the document and diff from GitHub for the duration of a request, holds them in memory, and serves them with private, no-store responses to the reviewer’s browser. Code still passes through the service in transit, so teams with stricter data requirements can self-host it.

The GitHub App is read-only for code and pull-request comments, and it does not use workflow files. The guided review does not replace GitHub’s merge process; the reviewer’s verdict and notes are recorded on the pull request, while merging remains in GitHub.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Review Assist MCP

review-assist-mcp is an MCP server that connects coding-agent sessions on a developer’s machine with GitHub pull-request reviews. Its main capabilities are authoring Intent Documents, validating them against the diff, and submitting review context for the companion GitHub App to present as a guided review.

Install it with your agent’s MCP command, such as `claude mcp add -s user review-assist -- npx -y review-assist-mcp` or `codex mcp add review-assist -- npx -y review-assist-mcp`. Install the GitHub App separately on the repository.

Yes, review-assist-mcp works with Claude Code. Register it with `claude mcp add`, or install the Review Assist Claude Code plugin, which includes the server and both review agents.

Yes, review-assist-mcp works with Codex. Add it with `codex mcp add`; Codex keeps its MCP configuration separate from Claude Code, so each agent must be registered independently.

Yes, Claude Desktop can install the published `.mcpb` package, and the VS Code extension can share the Claude Code or Codex configuration. On macOS, Dock-launched VS Code may require a global installation because GUI apps can have a restricted `PATH`.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewReview Assist MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/review-assist-mcp?style=directory)](https://allmcps.com/mcp/review-assist-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/review-assist-mcp"><img src="https://allmcps.com/api/badge/review-assist-mcp?style=directory" alt="Review Assist MCP on AllMCPs" /></a>