Gerrit MCP. Track code reviews and audit repo state from chat.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Gerrit MCP Server gives your AI agent full control over your entire code review process. It lets you query specific changes (e.g., all open changes by yourself), audit detailed patch sets, and check approval status without leaving your chat interface.
You can also list projects, branches, and groups to audit the repo structure directly.
What your AI agents can do
Get account
Fetches the authenticated user's profile information from Gerrit.
Get change
Retrieves all detailed data about a specific Gerrit code review change.
Get project
Gets full details and metadata for a specific Gerrit project.
Use query_changes to retrieve code review subjects, numbers, and owners based on specific criteria like status or owner.
Run list_patchsets to get a complete list of revisions for any change, including parent commits and commit SHAs.
Call list_reviewers to enumerate who reviewed a change and confirm specific approval labels (e.g., Verified).
List all projects (list_projects) and then list all branches (list_branches) within a project to verify repo boundaries.
Retrieve your own profile details (get_account), list associated emails (list_emails), or map all organizational groups (list_groups).
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Gerrit MCP Server: 10 Tools for Code Review & SCM
Use these tools to query change status, audit commit history, list projects, and verify branch dependencies within your Gerrit instance.
019d75a3get account
Fetches the authenticated user's profile information from Gerrit.
019d75a3get change
Retrieves all detailed data about a specific Gerrit code review change.
019d75a3get project
Gets full details and metadata for a specific Gerrit project.
019d75a3list branches
Lists every active branch within a specified Gerrit project.
019d75a3list emails
Retrieves all email addresses tied to the authenticated user account.
019d75a3list groups
Lists all groups in the Gerrit instance, showing ownership and permissions.
019d75a3list patchsets
Generates a full list of all revision history (patch sets) for a given code change.
019d75a3list projects
Retrieves a list of all repositories managed by Gerrit.
019d75a3list reviewers
Lists every person who has reviewed a specific code change.
019d75a3query changes
Queries code changes using syntax like 'status:open' or 'owner:self' to find specific reviews.
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 every 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 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Your AI agent gives you full control over your code reviews. You can query specific changes, audit detailed patch sets, and check approval status without ever leaving your chat. It also lets you list projects, branches, and groups to audit the whole repo structure.
Find and Filter Code Reviews: You can use query_changes to pull code review subjects, numbers, and owners based on criteria like status or owner. Trace Commit History: Running list_patchsets gives you a complete list of revisions for any change, including parent commits and commit SHAs. Monitor Reviewer Approvals: You call list_reviewers to see who reviewed a change and confirm if they slapped on specific approval labels, like Verified. Map Project and Branch Status: You list all projects with list_projects, then run list_branches on a project to verify repo boundaries. Audit User Accounts and Groups: You grab your own profile details using get_account, list associated emails with list_emails, or map every organizational group with list_groups.
How Gerrit MCP Works
- 1 Subscribe to the Gerrit MCP Server and provide your required Gerrit URL, Username, and HTTP Password.
- 2 Your AI agent uses a tool like
query_changesto send a request to the Gerrit API. - 3 The agent returns structured data containing the requested change subjects, numbers, or project metadata.
The bottom line is, your AI agent runs complex Gerrit API commands and translates the structured results into natural conversation.
Who Is Gerrit MCP For?
This is for the maintainer who needs to track open changes and audit code review progress without leaving their IDE. It's for the DevOps engineer who needs to verify project branch structures or the SRE team that needs to audit group permissions across the organization.
Uses query_changes to track their own open changes and list_patchsets to review the full history of a pull request.
Uses list_reviewers and query_changes to audit the collective progress of code reviews and confirm required approvals.
Uses list_projects and list_branches to verify repository metadata and test API integration points in real-time.
What Changes When You Connect
- Track open changes instantly. Use
query_changeswith filters likestatus:openorowner:selfto get a quick list of relevant code reviews. - See the full commit lineage.
list_patchsetsshows every revision (patch set) for a change, giving you commit SHAs and parent commits for detailed history. - Verify approvals before merge.
list_reviewerscounts reviewers and checks for specific labels (like Code-Review or Verified) on a change. - Audit the entire codebase.
list_projectslets you see all available repositories, andlist_brancheslets you check the latest SHA for a project's branches. - Manage identity context. Run
get_accountto fetch your own profile andlist_emailsto confirm associated email addresses. - Understand organizational structure.
list_groupsmaps all defined groups, helping you verify who controls access to which projects.
Real-World Use Cases
Need to check if a feature branch is ready for merge.
The engineer needs to know if the feature/auth branch is up to date. They ask their agent to run list_branches on the 'frontend-v2' project. The agent returns the latest commit SHA for all branches, allowing the engineer to confirm the target branch is current.
Auditing a critical bug fix requires knowing all changes.
The manager needs to verify the full history of fix #501. They prompt their agent to use list_patchsets on change #501. The agent returns every single revision, showing the commit SHA, the uploader, and all parent commits, ensuring no step was missed.
Checking if a PR has the necessary approvals before merge.
A developer submits a change and needs sign-off. They ask the agent to use list_reviewers on the change ID. The agent confirms the count of reviewers and checks for required labels like 'Verified', letting the developer know if they need more eyes on it.
Finding all projects owned by a specific team.
The architect needs a full inventory of all available repositories. They use list_projects to get a list of all projects, then use get_project on a specific ID to pull detailed metadata, giving them a clear view of the entire system scope.
The Tradeoffs
Manual API calls for status checks
Running separate API calls for project listing, then calling another endpoint for the branch list, and finally calling a third endpoint for the latest commit SHA. This requires manual chaining and fails if any single endpoint changes.
→
Use the agent to chain the calls. Start with list_projects to get the scope, then pass that result to list_branches to get the list, and finally use get_project to grab the specific metadata. Keep the interaction within the agent chat.
Assuming the current owner is the only owner
Only calling get_account and assuming that's the full picture of who can access the repo. This ignores group permissions and system-level access boundaries.
→
Always audit group access using list_groups and check resource ownership with list_reviewers to build a complete security picture.
Treating changes and projects as separate concepts
Just looking at a change ID without checking which project it belongs to. You get the history, but you don't know the context or the repository boundary.
→
Always use query_changes with project or owner filters (e.g., project:myproj) to ensure the change ID is scoped correctly before reviewing it.
When It Fits, When It Doesn't
Use this MCP Server if your primary need is deep, structured auditing of code review metadata, patch set history, or repository structure. Specifically, if you need to know who approved what, when, and how it changed, this is the tool. Don't use it if you simply need to read a project's README or manage deployment credentials—those are outside its scope. If your goal is just to check if a project exists, use list_projects. If you need to verify if a specific user is on the team, use get_account. If you need to see the full lifecycle of a change, you must use list_patchsets and list_reviewers together.
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 INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Tracking code changes means juggling a dozen different API endpoints.
Right now, checking a single code review means logging into Gerrit, finding the change ID, clicking 'History' to see the patch sets, then clicking 'Reviewers' to see approvals, and finally running a separate query to confirm the project status. It's a painful, multi-tab, copy-paste workflow.
With this MCP Server, you just ask your agent to 'Show me the review status for change #501.' The agent runs all the necessary tools—`list_reviewers`, `list_patchsets`, and `query_changes`—and gives you one clean summary.
Gerrit MCP Server: Full visibility into project and branch metadata.
Manually listing branches requires navigating to the project page, then finding the branch selector, and finally running a separate API call just to get the latest SHA. If you need to audit all projects, you repeat this entire process for every single repository.
Now, you tell your agent to 'List all projects and their branches.' It handles the `list_projects` and `list_branches` calls internally, giving you a full, structured map of your entire repository topology in seconds.
Common Questions About Gerrit MCP
How do I use the `query_changes` tool to find open changes? +
Use the syntax status:open in your prompt. This tells the agent to filter the results to only show code reviews that haven't been merged yet. You can combine this with owner:self to find only your open changes.
Can I check the full history of a change using `list_patchsets`? +
Yes, list_patchsets retrieves every revision associated with a change ID. It details the commit SHAs, the uploader, and the parent commits, giving you the complete historical record.
How does `list_reviewers` help me with approvals? +
list_reviewers shows exactly who reviewed the change. It also reports specific approval labels (like Verified or Code-Review), helping you confirm if the necessary sign-off was achieved.
What is the difference between `list_projects` and `list_branches`? +
list_projects gives you a list of all available repositories (the container). list_branches requires a specific project ID and lists the actual development lines within that container.
How do I use `get_account` to check my authenticated identity? +
It fetches your profile details and associated emails. This confirms which user context your agent is running under, which is critical for accurate change tracking and auditing.
What information does `list_groups` provide about project access? +
It returns group names, IDs, owners, and descriptions. This lets you audit who controls access to projects and understand the permission structure of your organization.
Can I use `query_changes` to filter by a specific owner? +
Yes, you can use syntax like owner:self or owner:username in the query. This limits the results to changes submitted by specific users, making targeted review easy.
How do I use `list_emails` to verify account context? +
This tool retrieves all verified email addresses linked to your account. Checking these ensures your agent is operating with the correct, fully authenticated user context.
Can my agent list open changes across all Gerrit projects? +
Yes. Use the 'query_changes' tool with the query 'status:open'. The agent will retrieve the global array of all matching changes, including subjects, numbers, and owners natively.
How do I see the approval labels (Code-Review, Verified) for a specific change via chat? +
Use the 'get_change' tool. It retrieves the full details of a Gerrit change, including the 'labels' section where you can see the Code-Review and Verified scores assigned by reviewers natively.
Can I check which groups have access to a specific project through the agent? +
Absolutely. Use the 'list_groups' tool to identify existing groups. While project access rules are often defined in the project settings, the agent can help you verify group definitions and ownership within your organizational tree flawlessly.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Targetprocess
Connect your AI to Apptio Targetprocess. Agile portfolio management natively from the terminal: track user stories, active bugs, and sprint iterations seamlessly.
Genderize
Predict the gender of a person based on their first name via AI agents with Genderize.io.
The Graph (Web3 Indexing)
Index and query blockchain data across EVM and Solana chains. Access transfers, holders, swaps, and custom subgraphs directly.
You might also like
Troops
Automate HR and recruitment workflows via Troops — manage job offers, candidates, contracts, and timesheets directly from your AI agent.
KeyCDN (Content Delivery Network)
Manage edge caching via KeyCDN — purge zones and URLs, manage pull zones, and monitor traffic bandwidth.
Scribe
Create step-by-step guides and SOPs automatically by recording your workflow and generating visual documentation instantly.