Codereviewbuddy vs GitVerse MCP
A side-by-side look at the Codereviewbuddy and GitVerse MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
G
GitVerse MCPVersion Control · Local subprocess (stdio)MCP server for GitVerse: repositories, pull requests, reviews, comments and CI60GoodAuth: api key requiredVerdict: choose Codereviewbuddy for version control work as a local process; choose GitVerse MCP 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 Codereviewbuddy when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You want tools like
summarize_review_status, triage_review_comments, get_thread.
GChoose GitVerse MCP when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
GITVERSE_TOKEN. - You want tools like
listRepositories, getRepository, getPullRequests.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | G GitVerse MCP | |
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 34/100 · Emerging | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | GITVERSE_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 10 | 27 |
| Full listing | View Codereviewbuddy | View GitVerse MCP |
Tools & capabilities
Codereviewbuddy tools 10
summarize_review_statusLightweight stack-wide overview — start heretriage_review_commentsOnly actionable inline threads needing attentionget_threadFull thread details by node ID — use after triage for conversation historyreply_to_commentReply to inline threads (`PRRT_`), PR-level reviews (`PRR_`), or bot comments (`IC_`)diagnose_ciDiagnose CI failures — finds the failed run, jobs, steps, and error lines in one callcheck_ci_statusLightweight CI pass/fail/pending check for a PR — use before mergingstack_activityChronological activity feed across a PR stack with a `settled` flaglist_recent_unresolvedScan recently merged PRs for unresolved review threadsreview_pr_descriptionsAnalyze PR descriptions for quality issues (empty body, boilerplate, missing linked issues)show_configShow active configuration with human-readable explanation
GitVerse MCP tools 27
listRepositoriesList repositories. Without arguments lists the authenticated user's repositories; pass org to list organization repositories. Supports page/per_page.getRepositoryGet details of a specific repository.getPullRequestsList pull requests of a repository. state filters by open/closed. Supports page/per_page.createPullRequestCreate a pull request from head to base. GitVerse has no reviewer requests — use assignees instead. Pass draft=true to create a draft.getPullRequestGet details of a specific pull request.updatePullRequestUpdate a pull request: title, body, state (open|closed), base branch. assignees and labels are applied through the issue endpoint because a PR is an issue in GitVerse.getPullRequestActivityGet the activity/timeline of a pull request.approvePullRequestApprove a pull request by submitting an APPROVED review.unapprovePullRequestRemove your approval: finds your latest APPROVED review on the pull request and deletes it.declinePullRequestDecline (close) a pull request. An optional message is posted to the discussion before closing.requestChangesRequest changes on a pull request by submitting a REQUEST_CHANGES review.removeChangeRequestRemove your change request by superseding it with an APPROVED review (GitVerse has no dedicated un-request endpoint).- +15 more on 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.
Codereviewbuddy
{
"mcpServers": {
"codereviewbuddy": {
"command": "uvx",
"args": [
"codereviewbuddy"
]
}
}
}
GitVerse MCP
{
"mcpServers": {
"grigoriy-grisha-gitverse-mcp": {
"command": "npx",
"args": [
"-y",
"@grigoriy-grisha/gitverse-mcp@latest"
],
"env": {
"GITVERSE_TOKEN": "YOUR_GITVERSE_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Codereviewbuddy is categorized under Version Control and uses a local stdio subprocess. GitVerse MCP belongs to Version Control and uses a local stdio subprocess. Pick Codereviewbuddy for version control work and GitVerse MCP 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.
Codereviewbuddy has no declared pricing — check the project's own site. GitVerse MCP has no declared pricing — check the project's own site. Auth: api key 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 codereviewbuddy and grigoriy-grisha-gitverse-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Codereviewbuddy has a quality signal of 34/100 (Emerging) with 1 views, 0 installs and 0 GitHub stars. GitVerse MCP has 60/100 (Good) with 1 views, 0 installs and 1 GitHub stars.