Gerrit MCP. Manage code reviews from conversation.
Gerrit MCP lets you manage every step of your code review process directly through conversation. Query changes by status or owner, track the full history of patch sets, audit approvals, and map out project branches without leaving your agent chat. It gives your AI client complete oversight of your entire Git workflow.
Give Claude and any AI agent real-world access
Find specific code reviews by status, owner, or project name using advanced search syntax.
Retrieve the complete list of patch sets for a change to track every commit SHA and parent revision in its lifecycle.
List who has reviewed a change and verify if necessary approval labels have been applied by team members.
Get metadata for all projects, list branches within a project, or check the latest commit SHAs to understand repo boundaries.
List associated user emails, audit system groups, or fetch detailed information about authenticated accounts.
Ask an AI about this
Waiting for input…
What AI agents can do with Gerrit: 10 Tools for Code Review Operations
These tools allow you to query specific data points within Gerrit, whether it's listing projects, retrieving user details, or tracking the commit history of a change.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Gerrit MCPQuery Changes
Find specific code reviews (changes) on Gerrit using advanced filters like status or owner.
Get Change
Retrieves the full, detailed information for a single specified change ID.
List Projects
Lists every project (repository) available on your Gerrit instance.
Get Project
Gets full, detailed metadata about a specific Gerrit project.
List Branches
Lists all defined branches within any given Gerrit project.
Get Account
Fetches the profile information for the currently authenticated Gerrit user account.
List Emails
Lists all email addresses associated with your verified Gerrit account.
List Reviewers
Retrieves a list of users who have reviewed a specific change.
List Patchsets
Lists all historical revisions (patch sets) for a change, including commit SHAs and...
List Groups
Returns the names, IDs, and ownership information for all defined groups in Gerrit.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Gerrit, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Gerrit. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The manual process of reviewing a single change is a nightmare.
Today, if you need to check one person's changes against three different branches and verify two required approvals, you open Gerrit. You find the change number; you switch tabs to see the list of reviewers; you run another query to get the patch set history, and then you have to manually cross-reference all that data—all before you can even start writing code.
With this MCP connected via Vinkius, you just ask your agent. 'What is the status of change #501?' The agent runs `get_change`, aggregates the reviewer list using `list_reviewers`, and summarizes the approval labels in one clean response. You get the answer immediately, without touching a browser tab.
Gerrit MCP Gives You Full Code Review Oversight
Gone are the days of having to manually cross-reference commit SHAs from different patch sets or running through multiple filter queries just to find an open change by owner. The agent handles all that data aggregation for you.
You don't just get a list; you get context. You ask, and it reports back on the project structure, the users involved, and the current state of approvals. It’s not just better—it fundamentally changes how fast your team can actually merge code.
What Gerrit MCP does for your AI
Need to keep tabs on what's being coded? This MCP connects your Gerrit instance directly to any AI agent, giving you total control over code reviews and repository management through natural conversation. Instead of opening dozens of browser tabs just to check status updates or commit SHAs, you talk to your agent.
You can ask for all open changes in a specific project, filtering by owner or status using syntax like 'status:open'. Need to verify who needs to approve something? Ask the agent to list reviewers and check if required labels, like 'Code-Review' or 'Verified', are present. It also helps you map out your repository structure; you can query all projects, list every branch in a project, and even audit user groups to see who has access control.
If you use Vinkius, you get this entire suite of developer tools connected once and accessible from any compatible client.
019d75a3-8ee0-70ec-a0e0-538d27e5fef4 How to set up Gerrit MCP
The bottom line is you manage complex code review tasks by talking to your agent instead of navigating multiple developer tools.
Subscribe to this MCP and provide your Gerrit URL, username, and HTTP password.
Connect the credentialed MCP to your preferred AI client (Claude, Cursor, etc.).
Use natural conversation to query changes, list branches, or check project details using specific syntax.
Who uses Gerrit MCP
This MCP is for the maintainer who gets burned out clicking through dashboards just to verify a merge status. It's also for the engineering manager who needs a quick, comprehensive view of team approval progress without logging into Gerrit.
Uses this MCP to check open changes and list patch sets directly within their chat or IDE interface when they don't want context switching.
Audits code review progress by asking the agent to enumerate reviewers and verify necessary approval labels across multiple pending merges.
Tests project boundaries by listing all projects, retrieving detailed metadata, or verifying group access permissions for CI/CD setup.
Benefits of connecting Gerrit MCP
You stop switching tabs. Instead of manually navigating to a change ID, you ask the agent to list all patch sets for that change, getting the full history and commit SHAs immediately.
Review status checks are instant. You can query changes using query_changes with syntax like 'status:open' so your agent only pulls exactly what needs reviewing, filtering out noise.
Approval tracking gets clearer. By calling list_reviewers, you instantly see who has provided feedback and verify if critical approval labels were added, without manually checking comments.
Project structure is visible at a glance. Use list_projects to get an overview of your entire repository landscape, or use list_branches to map out which branches exist in a given project.
Identity management simplifies. You don't need to remember user IDs; simply asking the agent for user information using get_account keeps context clean.
Gerrit MCP use cases
Checking merge readiness
An engineer needs to know if a change is ready to merge. They ask their agent, 'Who are the reviewers for change #123?' The agent uses list_reviewers and reports back on required approval labels, telling them exactly what's missing before they even open Gerrit.
Debugging version history
A maintainer suspects a specific commit SHA was overwritten. They ask the agent to list all patch sets for that change. The agent uses list_patchsets and gives them the full, chronological record of revisions, letting them pinpoint the exact moment something broke.
Auditing team access
A DevOps engineer needs to verify if a new contractor has access rights. They ask the agent to list all groups and then query group details using list_groups, verifying who controls what projects across the organization.
Finding stale changes
An engineering manager wants to clean up old, unreviewed code. They prompt the agent with 'List my open changes in the core API project.' The agent uses query_changes and provides a list of subjects, numbers, and owners that need attention.
Gerrit MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Treating it like a simple search engine
Asking the agent to just 'tell me about project X'. The response is usually vague or incomplete because you didn't specify what kind of data (metadata, branches, status) you actually needed.
Be specific. To check metadata, ask the agent to use get_project. If you need branch names, explicitly ask it to run list_branches for that project.
Ignoring authentication requirements
Assuming the agent can list all users or groups without proper credentials. This results in a generic 'permission denied' error and leaves you stuck.
Ensure your initial setup includes providing the necessary Gerrit URL, username, and HTTP password so the MCP can run get_account and access restricted data.
Mixing up projects and changes
Asking to 'list all commits' without specifying a project or change ID. The agent gets confused because commit history is tied to specific objects.
First, use list_projects to find the right repo name. Then, specify that project when querying: 'List open changes in [Project Name]' using query_changes.
When to use Gerrit MCP
Use this MCP if your daily workflow involves frequent status checks on code reviews and patch sets. If you need to know who reviewed a change, what the current branch state is, or why a merge is blocked due to missing approvals, this tool is essential. However, don't use it if all you need is general Git command execution (like pure git commit messages). For simple commits or local branching operations that haven't been pushed and reviewed, stick to your local CLI. This MCP excels at the coordination layer—the reading, auditing, and status checking of code that has already entered the official review pipeline.
Frequently asked questions about Gerrit MCP
How do I check my open Gerrit changes using the query_changes tool? +
You simply ask your agent to run query_changes and provide a filter, such as 'status:open' or 'owner:self'. The MCP handles the advanced syntax so you don't have to remember it.
Can I use Gerrit MCP to see all branches in a project? +
Yes. You ask the agent to list all projects first, then specify which one you want details on and run list_branches for that project's current state.
What is the difference between get_change and list_patchsets? +
The get_change tool gives you the high-level metadata (who, what, when). The list_patchsets tool drills down further to give you a full historical record of every commit SHA that contributed to that change.
Is Gerrit MCP useful for auditing group permissions? +
Absolutely. You can use the agent to run list_groups and then query specific groups to verify who has control over which parts of your organization's project access.
Does this MCP help with pull request workflows? +
Yes, it manages the core components of PR workflows. You can check approvals (list_reviewers) and track the full commit history required to complete a successful merge.