Gerrit Code Review vs Repowise
A side-by-side look at the Gerrit Code Review and Repowise MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gerrit Code Review for version control work; choose Repowise for version control as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Gerrit Code Review when
- You need dedicated capabilities in the Version Control domain.
- You have the keys it needs:
GERRIT_URL, GERRIT_USERNAME, GERRIT_TOKEN. - You want tools like
search_changes, get_change, list_change_files.
Choose Repowise when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 48/100 · Fair | 61/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | GERRIT_URLGERRIT_USERNAMEGERRIT_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 9 | 7,901 |
| Directory activity | 0 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 8 | Not listed |
| Full listing | View Gerrit Code Review | View Repowise |
Tools & capabilities
Gerrit Code Review tools 8
search_changesquery changes with Gerrit's change query syntax, paginated.get_changeone change in review-relevant detail: status, owner, labels with votes, current revision, messages.list_change_filesfiles touched by a revision, with per-file change stats.get_file_diffthe diff of one file in a revision.get_change_commentscomment threads on a change, with resolution state and comment ids. Returns unresolvedpost_commentspublish a review in one call: optional top-level message plus inline, range, file-level, andset_voteset a label vote (e.g. `Code-Review`) with an optional message; value `0` clears an own vote.transition_changemove a change's state: `submit`, `abandon`, `restore`, `wip`, or `ready`, with an optional
Repowise tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Gerrit Code Review
No confirmed install command for Gerrit Code Review yet — follow the setup steps linked from its listing page rather than a guessed package name.
Repowise
{
"mcpServers": {
"repowise-dev-repowise": {
"command": "uvx",
"args": [
"repowise"
]
}
}
}
Frequently asked questions
Gerrit Code Review is categorized under Version Control and uses an install path we have not confirmed yet. Repowise belongs to Version Control and uses a local stdio subprocess. Pick Gerrit Code Review for version control work and Repowise for version control.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Gerrit Code Review has no confirmed install command yet — follow its own setup instructions.
Gerrit Code Review has no declared pricing — check the project's own site. Repowise is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add gerrit-code-review and repowise-dev-repowise as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gerrit Code Review has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 9 GitHub stars. Repowise has 61/100 (Good) with 6 views, 0 installs and 7,901 GitHub stars.