How to Use the Gerrit MCP in CrewAI

Q: How do I give my CrewAI agents access to Gerrit?

Just pass your Vinkius MCP endpoint URL to the mcps parameter when defining your Agent. CrewAI handles the connection, and your agent can immediately start using tools like querychanges.

Deploy autonomous agent crews to monitor, audit, and report on your Gerrit code review lifecycle with CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Gerrit MCP to CrewAI

Create your Vinkius account to connect Gerrit to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Gerrit with CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Assign Gerrit Tasks to a Crew

Go beyond single-agent scripts. With CrewAI, you can create a 'Monitor' agent whose only job is to run `query_changes` every five minutes to find new reviews for a specific project. When it finds one, it passes the change ID to an 'Analyst' agent. That agent then uses `get_change`, `list_patchsets`, and `list_reviewers` to assemble a complete summary. This division of labor is how you build robust, autonomous systems.

Run Continuous Audits with an Agent Team

Set up a 'Compliance' crew. One agent uses `list_projects` to get a list of all repos. It passes each repo to a 'Branch-Auditor' agent that runs `list_branches` to check for old, unmerged branches. The crew's 'Reporter' agent can then take the findings and format a daily digest. Because CrewAI agents share context, they can collaborate on a single report without you orchestrating every step. This MCP server provides the raw data for them to work with.

Let Your CrewAI Agents Manage Reviews

A crew can manage the entire lifecycle before approval. An agent can spot a new change with `query_changes`, then use `get_change` to see if it has the "WIP" (work-in-progress) label. If the WIP label is removed, the crew can be tasked to find appropriate reviewers using `list_groups` based on the project, then use another tool to notify them. It turns your agents from passive observers into active participants in your workflow.

Setup guide

Set up Gerrit MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Gerrit tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Gerrit Analyst",
    goal="Access and analyze Gerrit data via MCP.",
    backstory="Expert analyst with direct Gerrit access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Gerrit transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

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

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Gerrit Analyst",
        goal="Access and analyze Gerrit data via MCP.",
        backstory="Expert analyst with direct Gerrit access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Gerrit transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

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

Get your connection token →

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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Gerrit now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Gerrit MCP in CrewAI

Just pass your Vinkius MCP endpoint URL to the `mcps` parameter when defining your Agent. CrewAI handles the connection, and your agent can immediately start using tools like `query_changes`.

Yes, that's exactly what it's for. Create a 'Scout' agent that uses `query_changes`. Its task output, a list of change IDs, can be the input for an 'Analyst' agent that uses `get_change`.

No. This MCP server provides read-only tools for your crew. They can monitor changes and report on status using `get_change`, but they cannot write comments or approve changes in Gerrit.

No. You configure the authentication once with the single MCP URL from Vinkius. Every agent in your crew that uses that server is automatically authenticated.

Your crew will only ever see Gerrit metadata. This includes information about code reviews, patch sets, project settings, and user accounts. The server is sandboxed and never has access to your actual source code.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript