A
licenseNot graded
qualityF
maintenanceProvides integration with Gerrit code review system, allowing AI assistants to fetch change details and compare patchset differences for code reviews.
38
MIT
Gerrit MCP Server
OfficialRelated Servers
Alternatives to Gerrit MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables language models to query and manage Gerrit code reviews via the REST API.1Apache 2.0
- FlicenseNot gradedqualityAmaintenanceA Model Context Protocol server that connects AI coding agents to Gerrit code review, enabling change search, diff review, and comment publishing without leaving the session.-
- AlicenseNot gradedqualityAmaintenanceAn MCP server that exposes Gerrit code review operations as capability-gated tools, enabling AI agents to search and read changes, publish comments, vote, and manage change state, with write capabilities as explicit opt-in.8MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for OpenDev Gitea and Gerrit APIs, enabling repository browsing, code review, and change management for LLM agents.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to query and manage GitLab projects, issues, merge requests, and file contents via the GitLab REST API v4.2 npmMIT
TDQS
B3/5.0
Scored across 25 tools
Disambiguation4/5
Most tools target distinct actions and resources, but there is minor overlap between query_changes and query_changes_by_date_and_filters, and between delete_draft_comments (all) and delete_draft_comment (single). The descriptions clarify these boundaries, so an agent can generally select correctly.
Naming Consistency4/5
The overwhelming majority follow a verb_noun pattern (query_, get_, list_, delete_, set_, create_, etc.). The notable exception is 'changes_submitted_together', which is a noun phrase rather than a verb-first name, and 'query_changes_by_date_and_filters' is longer but still verb-initial.
Tool Count3/5
With 25 tools, the server sits at the high end of what is typically considered heavy. While each tool has a specific purpose for Gerrit operations, the count is borderline and may feel bloated compared to more focused servers.
Completeness4/5
The server covers the core Gerrit lifecycle well: create, query, get details, modify state, comment, add reviewers, revert, and abandon. However, it lacks a direct 'submit' operation, which is a notable gap for a Gerrit client, and also misses actions like restoring an abandoned change or editing a commit message.
Maintenance
ActivitySlowing
ResponsivenessUnresponsive