Fetching the diff is table stakes; submit_gerrit_review is what makes this a full loop, letting an assistant leave a Code-Review vote and comments anchored to specific lines, with control over who gets notified. Comparing two patchsets is the other useful piece for tracking how a change evolved across review rounds. Excluding noisy file types keeps large binaries out of the review.
A server over the Gerrit code review system: fetch a change and its diffs, compare patchsets, and submit review feedback.
- fetch_gerrit_change returns a change's files, patch sets and diffs, with project, branch, author, reviewers and history, and can target a specific patchset
- fetch_patchset_diff compares two patchsets of a change, whole or for one file
- submit_gerrit_review posts summary feedback, vote labels such as {"Code-Review": 1}, and inline or file-level comments
- The review can target a patchset and control notification scope — NONE, OWNER, OWNER_REVIEWERS or ALL
- Comment payloads take a path, message and optional Gerrit fields like line, side and range
Python 3.10+ (3.11 recommended) and Gerrit HTTP access — GERRIT_HOST, GERRIT_USER and GERRIT_HTTP_PASSWORD, the last generated from Gerrit's HTTP Credentials. GERRIT_EXCLUDED_PATTERNS optionally excludes file types from reviews. Clone, create a venv, pip install -e ., then the client launches server.py with --transport stdio.
One command plus a key — npx -y @smithery/cli install @cayirtepeomer/gerrit-code-review-mcp --client claude, then supply credentials