# ReviewGate/reviewgate [Health: Active]

**Category:** 🔄 Version Control  
**Repository:** https://github.com/ReviewGate/reviewgate  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/reviewgate-reviewgate

## Description
Code review against the rules your team actually wrote, not generic best practice. A cheap generator finds problems, an independent judge refutes them against full files, so the noise stays down. Two tools for the agent loop (getteamrules, reviewchanges), plus a pre-push gate and a bot on GitLab/GitHub pull requests. Single binary, no Node or Docker; bring your own model key.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What ReviewGate/reviewgate MCP server does

ReviewGate/reviewgate MCP server applies a team's own review rules to code changes. Those rules can come from ADRs, repository conventions, and `.reviewgate/config.yml`. The project is intended for reviews that reflect written engineering agreements instead of broad, model-generated best practices.

The MCP interface is one part of a wider review workflow. The same review approach is also available through the `reviewgate review` CLI command, a pre-push gate, and a bot that posts reviews on GitHub or GitLab pull requests. The repository distributes compiled release binaries; its source code is not published.

## How it works

An agent can request the team's rules and submit changes for review during its work. ReviewGate first uses a lower-cost generator to identify possible problems. A separate, stronger judge then checks those candidates against the complete files and the configured rules. Only findings that survive that second check are published.

This design is aimed at reducing findings that are technically plausible but unrelated to the standards maintained by a particular team. The MCP workflow runs before a pull request is created, while the CLI, hook, and pull-request bot cover later stages of the same process.

## Setup and configuration

The documented Claude Code installation uses the ReviewGate marketplace plugin:

```text
/plugin marketplace add ReviewGate/reviewgate
/plugin install reviewgate@reviewgate
```

The equivalent shell commands are `claude plugin marketplace add ReviewGate/reviewgate` and `claude plugin install reviewgate@reviewgate`. The plugin requires the ReviewGate CLI binary, which is downloaded as a platform-specific release, placed on `PATH`, and checked with `reviewgate doctor`. Available release targets include macOS, Linux, and Windows variants.

ReviewGate requires a model key supplied by the user. It also documents a self-hosted pull-request bot, installed with Docker Compose, but does not provide the bot's environment-variable list in this repository excerpt.

## Tools and capabilities

The MCP tools are:

- `get_team_rules` — retrieves the rules the agent should use for review.
- `review_changes` — asks ReviewGate to inspect the current changes against those rules.

The CLI can review staged, uncommitted, or committed changes. A pre-push hook can reject a push containing blocking findings. The GitHub and GitLab bot can publish a summary, inline findings, one-click fixes, and a merge gate.

## Limitations and notes

ReviewGate/reviewgate is self-hosted and requires you to provide a model key; the material does not identify a built-in model provider. The release repository contains binaries rather than the application source.

These statements describe the project's documented deployment model and should be checked against the linked security documentation when evaluating it for a sensitive environment.

_Full upstream README: https://allmcps.com/mcp/reviewgate-reviewgate/readme_