Git MCP vs ReviewGuard
A side-by-side look at the Git MCP and ReviewGuard MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Git MCP for version control work as a local process; choose ReviewGuard 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 Git MCP 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.
Choose ReviewGuard when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_pr_review_context, list_pending_review, add_review_comments.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 49/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 8,472 | 4 |
| Directory activity | 7 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 7 |
| Full listing | View Git MCP | View ReviewGuard |
Tools & capabilities
Git MCP tools
No tool names declared yet. Check the project README from the listing page.
ReviewGuard tools 7
get_pr_review_contextGet PR author/message, submitted review summaries, inline review threads with resolved state, reactions and permalinks, and general PR commentslist_pending_reviewList the authenticated user's pending draft review, including all current pending review comments and their permalinksadd_review_commentsAdd one or more comments to the authenticated user's pending review, creating the pending review if neededmodify_review_commentUpdate or delete one comment from the authenticated user's pending reviewdelete_pending_reviewDelete the authenticated user's pending review and all its commentssubmitSubmit the pending review as a real, posted review. The `action` is limited to the allowed set and the review summary always starts with the fixed, server-configured disclaimerresolve_review_threadResolve one of the authenticated user's **own** review threads (e.g. a prior finding the latest push fixed). Refuses threads started by anyone else
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.
Git MCP
{
"mcpServers": {
"idosal-git-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote"
]
}
}
}
ReviewGuard
{
"mcpServers": {
"reviewguard": {
"command": "npx",
"args": [
"-y",
"@eclipsesource/review-guard-mcp"
]
}
}
}
Frequently asked questions
Git MCP is categorized under Version Control and uses a local stdio subprocess. ReviewGuard belongs to Version Control and uses a local stdio subprocess. Pick Git MCP for version control work and ReviewGuard 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.
Git MCP is listed as free. Auth: no auth required. ReviewGuard has no declared pricing — check the project's own site. 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 idosal-git-mcp and reviewguard as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Git MCP has a quality signal of 49/100 (Fair) with 7 views, 0 installs and 8,472 GitHub stars. ReviewGuard has 57/100 (Good) with 1 views, 0 installs and 4 GitHub stars.