Google Git
Sign in
gerrit/gerrit-mcp-server/2d2f63d6fb0174d60c4ba4c1c2935bc93bc76bea
commit
2d2f63d6fb0174d60c4ba4c1c2935bc93bc76bea
[log]
author
Nasser Grainawi <nasser.grainawi@oss.qualcomm.com>
Mon May 04 15:33:59 2026 -0700
committer
Nasser Grainawi <nasser.grainawi@oss.qualcomm.com>
Tue Aug 11 16:45:55 2026 -0700
tree
8d519eac7241cf633e3cd9675ba83aa0cc497232
parent
347bc50371251f4e0c193b914a93ee534ba186f6 [diff]
Add get_git_parent_changes tool with structured output

Adds a new MCP tool that queries immediate git-parent changes of a given
change using Gerrit's `parentof:` query operator. Useful when navigating
a stack: given a change ID, it surfaces which open Gerrit changes have a
commit that is a direct parent of the queried change. Only immediate
parents are returned; grandparents and higher ancestors are excluded by
design.

Returns a typed _GitParentChangesResult so the MCP SDK auto-generates an
output_schema and produces both structured and unstructured text
content. Error paths raise exceptions rather than returning text error
content blocks. This follows the structured-output pattern documented
in AGENTS.md and the writing-extensions skill.

Includes tests/unit/test_get_git_parent_changes.py covering success, WIP
flag, multiple parents, empty result, JSON decode error, and curl
exception cases.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Change-Id: I61e8703d6dfb2f5aee2135b3a2d6c0a3bea7bf19
4 files changed
tree: 8d519eac7241cf633e3cd9675ba83aa0cc497232
  1. .claude/
  2. .claude-plugin/
  3. .gemini/
  4. docs/
  5. gerrit_mcp_server/
  6. gerrit_mcp_server_task/
  7. hooks/
  8. skills/
  9. tests/
  10. .gitignore
  11. .mcp.json
  12. AGENTS.md
  13. build-gerrit.sh
  14. gemini-cli-config.template.json
  15. gemini-extension.json
  16. LICENSE
  17. OWNERS
  18. pyproject.toml
  19. README.md
  20. server.sh
  21. uv.lock
README.md

🐍 Gerrit MCP Server

An MCP (Model Context Protocol) server for interacting with the Gerrit code review system. This server allows a language model like Gemini to query changes, retrieve details, and manage reviews by executing curl commands against the Gerrit REST API.

This server can be run as a persistent HTTP server or on-demand via STDIO.

📚 Documentation

For detailed information, please see the documents in the docs/ directory:

  • Configuration: A detailed guide to the gerrit_config.json file and all authentication methods.
  • Testing Guide: Instructions on how to run the unit, integration, and E2E tests.
  • Gemini CLI Setup: How to configure the Gemini CLI to use this server.
  • Claude Code Setup: How to use this server as a Claude Code plugin.
  • Best Practices: Tips for using the server effectively.
  • Contributing: Guidelines for contributing to the project.
  • Available Tools: A list of all available tools and their descriptions.
  • Extensions: How to register additional MCP tools without modifying the core server.
  • Example Use Cases: Scenarios demonstrating how to use the server.

🚀 Getting Started

1. Prerequisites

Before you begin, ensure you have the following tools installed and available in your system's PATH.

  • Python 3.12+: Required by the server.
  • uv: Used for dependency management and running the server. Optional — the build script will install it via pip if absent.
  • curl: The standard command-line tool for transferring data with URLs.

2. Build the Environment

Run the build script from the root of the gerrit-mcp-server project directory. This will create a virtual environment in .venv via uv sync and install all dependencies.

./build-gerrit.sh

3. Configure the Server

You will need to create a gerrit_config.json file inside the gerrit_mcp_server directory. Copy the provided sample file gerrit_mcp_server/gerrit_config.sample.json and customize it for your environment. See the Configuration Guide for details on all available options.

cp gerrit_mcp_server/gerrit_config.sample.json gerrit_mcp_server/gerrit_config.json

Alternatively, if your harness supports skills (tested with Claude Code), the /gerrit:setup skill can create or repair this file for you interactively. See Interactive Setup.

4. Run the Server (HTTP Mode)

To run the server as a persistent background process, use the server.sh script:

  • Start the server:
    ./server.sh start
  • Check the status:
    ./server.sh status
  • Stop the server:
    ./server.sh stop

For on-demand STDIO mode, please see the Gemini CLI Setup Guide or, to use this server as a Claude Code plugin, the Claude Code Setup Guide.

Security

This is not an officially supported Google product. This project is not eligible for the Google Open Source Software Vulnerability Rewards Program.