Skip to main content
Glama
GerritCodeReview

Gerrit MCP Server

Official

Related Servers

Alternatives to Gerrit MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables a language model to query code changes, retrieve details, and manage reviews by executing curl commands against the Gerrit REST API, and can run either persistently over HTTP or on demand via STDIO.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      An 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.
      9
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for OpenDev Gitea and Gerrit APIs, enabling repository browsing, code review, and change management for LLM agents.
      Apache 2.0

    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

    ActivityMaintained
    ResponsivenessUnresponsive