Gerrit Review MCP Server

What is Gerrit Review MCP Server?

This MCP server integrates with the Gerrit code review system, enabling AI assistants to fetch change details, compare patchsets, and submit review feedback through a set of tools.

How to use Gerrit Review MCP Server?

Install via Smithery (npx -y @smithery/cli install @cayirtepeomer/gerrit-code-review-mcp --client claude) or manually by cloning the repo, creating a virtual environment, and running pip install -e .. Configure environment variables (GERRIT_HOST, GERRIT_USER, GERRIT_HTTP_PASSWORD, optionally GERRIT_EXCLUDED_PATTERNS, GERRIT_SSL_VERIFY, GERRIT_CA_BUNDLE) and add the server to your ~/.cursor/mcp.json or .roo/mcp.json. The server exposes three tools: fetch_gerrit_change, fetch_patchset_diff, and submit_gerrit_review.

Key features of Gerrit Review MCP Server

• Fetch complete change details with files and diffs.
• Compare differences between two patchsets.
• Submit review feedback with labels and inline comments.
• Control Gerrit notification scope (NONE, OWNER, OWNER_REVIEWERS, ALL).
• Exclude file patterns from reviews (e.g., .pbxproj$, node_modules/).
• Support for self-signed TLS certificates and custom CA bundles.

Use cases of Gerrit Review MCP Server

• AI-powered code review of specific Gerrit changes and patchsets.
• Track code evolution by comparing patchset versions.
• Automate review feedback with votes, inline comments, and notifications.
• Filter out large generated files from review scope using exclusion patterns.

FAQ from Gerrit Review MCP Server

What are the prerequisites?

Python 3.10+, Gerrit HTTP access credentials (username and HTTP password generated from Gerrit settings), and access to the mcp[cli] package repository.

How does authentication work?

The server uses HTTP digest authentication with the credentials set in GERRIT_USER and GERRIT_HTTP_PASSWORD. If authentication fails, check that Gerrit's gitBasicAuthPolicy is set to HTTP or HTTP_LDAP.

Can I use self-signed certificates?

Yes. Set GERRIT_SSL_VERIFY=false to disable TLS verification (temporary workaround), or provide a custom CA bundle via GERRIT_CA_BUNDLE=/path/to/ca.pem to keep verification enabled.

What transport does the server use?

The server is configured with --transport stdio and communicates over standard input/output.

How are connection issues diagnosed?

Verify GERRIT_HTTP_PASSWORD, GERRIT_HOST (hostname only, no https://), ensure HTTPS access is enabled, and test with curl -u "user:pass" https://gerrit.example.com/a/changes/?q=status:open.