ReviewGuard

What ReviewGuard MCP server does

ReviewGuard MCP server places a controlled MCP interface between an AI agent and GitHub pull request review operations. The server holds the write-enabled GitHub token, so the agent does not receive the credential directly. Its tool set is limited to reading pull request context, managing the authenticated user's pending review, optionally submitting that review, and optionally resolving the user's own review threads.

The default workflow is human-reviewed drafting. An agent can inspect the pull request and create or revise inline comments, but those comments stay in a pending review and are not visible to other GitHub users. A human can then open the pull request, inspect the draft, and submit it.

How it works

The server supports two operational modes. Pending mode is the default: the submit tool is not registered, and the underlying client rejects submission attempts. This makes publishing a review unavailable through the MCP interface.

Submit mode is enabled with --allow-submit. The administrator supplies the permitted actions from approve, comment, and reject; the tool exposes only those choices. Every submitted review begins with a fixed server-configured disclaimer, while the agent can append its own summary. The --allow-resolve option separately enables resolution of threads whose first comment was authored by the authenticated user. Threads created by other users cannot be resolved.

For tighter isolation, --repo and --pr bind the server to one repository and pull request. Both options are required together. When configured, tool calls no longer accept repository and pull request selectors, and the client independently enforces the same boundary.

Setup and configuration

ReviewGuard MCP server requires Node.js 22 or newer. Install the published package globally with npm install -g @eclipsesource/review-guard-mcp, or run it through npx. Source installation requires npm 12 or newer and uses the repository's build and link steps.

For IDE use, run the server in stdio mode as a child process with npx -y @eclipsesource/review-guard-mcp --stdio. It can also run over Streamable HTTP with review-guard-mcp --port 4000; the default bind address is localhost. A separate --host value can bind to a specified address. HTTP requests are stateless and use the printed /mcp endpoint.

Autonomous deployments should combine --allow-submit with explicit allowed actions and, where appropriate, --repo and --pr. --submit-body changes the fixed disclaimer prefix and requires submit mode with non-empty text. If omitted, the server supplies a default disclaimer.

Tools and capabilities

• get_pr_review_context reads the author and description, submitted review summaries, inline threads and resolution state, reactions, permalinks, and general comments.
• list_pending_review returns the authenticated user's draft review and its current comments.
• add_review_comments creates or extends a pending review with one or more comments.
• modify_review_comment edits or removes one pending comment.
• delete_pending_review removes the pending review and all of its comments.
• submit publishes the pending review when submit mode permits it.
• resolve_review_thread resolves an eligible thread belonging to the authenticated user.

Limitations and notes

The package is a local installation rather than a hosted MCP service; its registry entry describes the npm package and local execution. Submission is disabled unless explicitly enabled at startup. Even in submit mode, the allowed action set is fixed when the server starts, and the disclaimer cannot be removed by the agent. Thread resolution is limited to the authenticated user's own threads.