Google Git
Sign in
gerrit/gerrit-mcp-server/refs/heads/master
commit
da6ae7b64c6f4e643754454a8a546bc82882f240
[log]
author
Nasser Grainawi <nasser.grainawi@oss.qualcomm.com>
Fri Jun 26 10:16:11 2026 -0700
committer
Nasser Grainawi <nasser.grainawi@oss.qualcomm.com>
Tue Aug 11 17:18:09 2026 -0700
tree
7bbab1c4bd4c6d916ac5306844a9ef8801a6c09c
parent
0f96c199e485b848b611466452ae6c14dd9578ac [diff]
Add code-owners plugin as an extension

Adds a new sibling package `gerrit_mcp_server_code_owners` wrapping the
Gerrit code-owners plugin REST API. `register()` wires up three tools,
all gated via `@requires_plugin("code-owners")`:

- `get_code_owner_status`: per-file ownership status for a change
  (APPROVED/PENDING/INSUFFICIENT_REVIEWERS), with pagination via
  `limit` and `start`.
- `get_code_owners_for_path`: suggested owners for a specific path in a
  change revision, filtered and ranked by the plugin (current reviewers
  ranked higher, change owner and service users excluded).
- `check_code_owner`: checks code ownership for a path in a branch,
  returning ownership kind (global/default/fallback) and optional
  change-level permissions when `change_id` is supplied.

All tools return typed TypedDicts so the MCP SDK auto-generates an
output_schema and emits both structured and unstructured content. Error
paths raise exceptions rather than returning text error payloads.

Includes 23 unit tests and updates docs/available_tools.md.

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