Google Git Google Git
Sign in
gerrit/gerrit-mcp-server/refs/heads/master
commit
e22d6dddd9e8a9fc8f889d4ca5ca709c43abe877
[log]
author
Yevhenii Yatchenko <yevhenii.yatchenko@gmail.com>
Mon Oct 19 14:30:03 2026 +0300
committer
Yevhenii Yatchenko <yevhenii.yatchenko@gmail.com>
Fri Oct 23 14:36:34 2026 +0300
tree
ba2e99fb59b7e981e81717a20e84693516bca9ff
parent
9f871dc769372c8c1543fec1633c1cf9f8a5f229 [diff] 
Make uv pick a Python below 3.15

The project names no Python version for uv. Where no Python 3.12 or
newer is installed, as on the Zuul nodes, uv sync downloads the newest
Python. Since the release of Python 3.15.0, uv sync downloads 3.15.

uv.lock holds no Python 3.15 wheel of cffi 2.0.0, pydantic-core 2.46.4,
or rpds-py 0.30.0. uv sync then builds cffi from source, which fails
without the libffi headers. As a result, every job of every change
fails before its tests run.

.python-version makes uv pick Python 3.12, 3.13, or 3.14, which every
locked package has wheels for. The Zuul nodes have none of them, so uv
downloads 3.14 there.

A .venv already built on Python 3.12 or 3.13 stays as it is, and a
local Python 3.12 or 3.13 needs no download. With 3.14 alone in
.python-version, uv would rebuild such a .venv on 3.14. With Python
downloads disabled, uv would also need an installed 3.14.

Change-Id: Ia578af324678d3d195b881c2602bd3d1bf5783c8
1 file changed
tree: ba2e99fb59b7e981e81717a20e84693516bca9ff
  1. .claude/
  2. .claude-plugin/
  3. .gemini/
  4. .zuul.d/
  5. docs/
  6. gerrit_mcp_server/
  7. gerrit_mcp_server_code_owners/
  8. gerrit_mcp_server_depends_on/
  9. gerrit_mcp_server_task/
  10. hooks/
  11. skills/
  12. tests/
  13. .gitignore
  14. .mcp.json
  15. .python-version
  16. AGENTS.md
  17. build-gerrit.sh
  18. gemini-cli-config.template.json
  19. gemini-extension.json
  20. LICENSE
  21. OWNERS
  22. pyproject.toml
  23. README.md
  24. requirements.txt
  25. server.sh
  26. 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.