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.

Gerrit MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Gerrit
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Gerrit through Vinkius, pass the Edge URL in the `mcps` parameter and every Gerrit tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Gerrit Specialist",
    goal="Help users interact with Gerrit effectively",
    backstory=(
        "You are an expert at leveraging Gerrit tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Gerrit "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Gerrit MCP Server

Connect your Gerrit Code Review instance to any AI agent and take full control of your collaborative code reviews, project repositories, and patch set management through natural conversation.

When paired with CrewAI, Gerrit becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Gerrit tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Change & Review Orchestration — Query Gerrit changes using advanced syntax like 'status:open' or 'owner:self' to retrieve subjects, numbers, and owners natively
Patch Set Auditing — List all revisions (patch sets) of a change to track commit SHAs, uploader info, and parent commits for detailed version history flawlessly
Reviewer & Approval Oversight — Enumerate reviewers on any change and retrieve approval labels (Code-Review, Verified) to monitor the consensus process synchronousy
Project & Repository Navigation — List all projects and retrieve detailed metadata including states (ACTIVE/READ_ONLY) and default branch configurations securely
Branch Management — Identify and list all branches within a Gerrit project, extracting the latest commit SHAs to verify repository boundaries natively
Account & Identity Discovery — Fetch authenticated user profile information and list associated verified email addresses to verify account contexts flawlessy
Group & Access Auditing — List all Gerrit groups to identify who controls access to projects and grants specific permissions within your organizational tree

The Gerrit MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Gerrit to CrewAI via MCP

Follow these steps to integrate the Gerrit MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 10 tools from Gerrit

Why Use CrewAI with the Gerrit MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Gerrit through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Gerrit + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Gerrit MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Gerrit for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Gerrit, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Gerrit tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Gerrit against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Gerrit MCP Tools for CrewAI (10)

These 10 tools become available when you connect Gerrit to CrewAI via MCP:

get_account

Get the authenticated Gerrit account

get_change

Get full details of a Gerrit change

get_project

Get full details of a Gerrit project

list_branches

List all branches in a Gerrit project

list_emails

List all email addresses associated with the authenticated Gerrit account

list_groups

Returns group names, IDs, owners, and descriptions. List all groups on Gerrit

list_patchsets

List all patch sets (revisions) of a Gerrit change

list_projects

List all projects (repositories) on Gerrit

list_reviewers

List all reviewers on a Gerrit change

query_changes

Uses syntax: "status:open", "owner:self", "project:myproj". Returns subjects, numbers, statuses, owners, projects, patches. Query changes (code reviews) on Gerrit

Example Prompts for Gerrit in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Gerrit immediately.

"List my open changes in project 'core-engine'"

"Who are the reviewers for change #501?"

"List all branches in project 'frontend-v2'"

Troubleshooting Gerrit MCP Server with CrewAI

Common issues when connecting Gerrit to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Gerrit + CrewAI FAQ

Common questions about integrating Gerrit MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.