Gerrit Review MCP Server

Created By
cayirtepeomera year ago
This MCP server provides integration with Gerrit code review system, allowing AI assistants to review code changes and their details through a simple interface.
Overview

What is Gerrit Review MCP Server?

Gerrit Review MCP Server is a tool that integrates with the Gerrit code review system, enabling AI assistants to review code changes and their details through a user-friendly interface.

How to use Gerrit Review MCP Server?

To use the server, install it via Smithery or manually, configure your environment variables, and then utilize the provided functions to fetch change details or compare patchsets.

Key features of Gerrit Review MCP Server?

  • Fetch complete change information including files and patch sets.
  • Compare differences between two patchsets of a change.
  • Detailed diff information for each modified file.
  • Supports reviewing specific patch sets and tracks evolution of changes.

Use cases of Gerrit Review MCP Server?

  1. Reviewing code changes in a collaborative environment.
  2. Analyzing code modifications across different versions.
  3. Streamlining the code review process for development teams.

FAQ from Gerrit Review MCP Server?

  • What are the prerequisites for using this server?

You need Python 3.10 or higher, Gerrit HTTP access credentials, and access to the mcp[cli] package repository.

  • How do I install the server?

You can install it via Smithery or manually by cloning the repository and setting up a virtual environment.

  • What should I do if I encounter connection issues?

Verify your HTTP password, check the GERRIT_HOST setting, and ensure HTTPS access is enabled on the Gerrit server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
cayirtepeomer
Star
7
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago