Gerrit OpenAPI MCP
Related Servers
Alternatives to Gerrit OpenAPI MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables interaction with Gerrit code review system via REST API, allowing language models to query changes, retrieve details, and manage reviews.2524Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables a language model to query code changes, retrieve details, and manage reviews by executing curl commands against the Gerrit REST API, and can run either persistently over HTTP or on demand via STDIO.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server that exposes Gerrit code review operations as capability-gated tools, enabling AI agents to search and read changes, publish comments, vote, and manage change state, with write capabilities as explicit opt-in.9MIT
- AlicenseNot gradedqualityDmaintenanceProvides integration with Gerrit code review system, allowing AI assistants to fetch change details and compare patchset differences for code reviews.38MIT
- AlicenseAqualityDmaintenanceProvides MCP tools to review git changes using OpenAI Codex CLI, enabling code review of unstaged, staged, or last-commit changes.39 npmMIT
- AlicenseAqualityCmaintenanceLets MCP clients such as Claude or ChatGPT find the pull requests waiting on your review, read their details and changed files, check CI status, post comments, and submit approve, request-changes, or comment reviews. It runs locally over stdio with a personal token or as a remote server with its own OAuth 2.1 authorization server (PKCE, dynamic client registration, per-client consent, and refresh-token rotation) so GitHub is only used to sign the user in.6MIT
TDQS
Scored across 173 tools
With 173 tools there is heavy structural overlap: getChangesChangeIdReviewers vs getChangesChangeIdRevisionsRevisionIdReviewers, getChangesChangeIdComments vs the per-revision comments, and getAccountsAccountId vs getAccountsAccountIdDetail/State/Name all target closely-related data. The presence of a literal getChangesChangeIdRevisionsRevisionIdReviewersReviewerId_2 suffix signals near-duplicate tools an agent cannot easily distinguish. Descriptions are precise individually but the sheer volume of near-identical reviewer/comment/diff variants makes misselection likely.
Names are mechanically generated path concatenations in camelCase (getChangesChangeIdRevisionsRevisionIdFilesFileIdDiff) mixed with snake_case namespace prefixes (code_owners_, checks_), so conventions are not unified. The get-verb prefix is used throughout but conveys little since almost every tool is a read. Length and case mixing break any clean verb_noun pattern.
173 tools for a single server is a massive, machine-dumped surface far beyond what an agent can navigate coherently. It is essentially an entire REST API flattened into one namespace rather than a curated tool set. This is the extreme-mismatch end of the scale.
Read coverage is exhaustive (accounts, changes, projects, groups, config, plugins), but the surface appears to be get-only with no create/update/delete operations—no posting reviews, submitting changes, creating changes, or adding reviewers. For a code-review domain this leaves critical write workflows as dead ends despite the enormous read surface.