Gitwand vs MCP Gitlab
A side-by-side look at the Gitwand and MCP Gitlab MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gitwand for version control work as a local process; choose MCP Gitlab 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 Gitwand when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You want tools like
gitwand_status, gitwand_resolve_conflicts, gitwand_preview_merge.
Choose MCP Gitlab 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:
GITLAB_URL, GITLAB_TOKEN, GITLAB_PAT, GITLAB_PERSONAL_ACCESS_TOKEN, GITLAB_API_TOKEN, MCP_READ_ONLY, GITLAB_READ_ONLY, GITLAB_AUTH. - You want tools like
gitlab_get_project, gitlab_create_project, gitlab_delete_project.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 60/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Free | Not declared |
| Required env vars | None listed | GITLAB_URLGITLAB_TOKENGITLAB_PATGITLAB_PERSONAL_ACCESS_TOKENGITLAB_API_TOKENMCP_READ_ONLYGITLAB_READ_ONLYGITLAB_AUTH |
| Verified owner | Community listing | Community listing |
| GitHub stars | 186 | 6 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 7 | 80 |
| Full listing | View Gitwand | View MCP Gitlab |
Tools & capabilities
Gitwand tools 7
gitwand_statusList conflicted files with their complexity and auto-resolvabilitygitwand_resolve_conflictsAuto-resolve trivial conflicts, return DecisionTrace + pendingHunksgitwand_preview_mergeDry-run resolution — stats and risk assessment without writing filesgitwand_explain_hunkExplain why a specific hunk was classified its type (full trace + context)gitwand_apply_resolutionApply a custom (LLM-provided) resolution to a specific complex hunkgitwand_resolve_hunkAsk the connected agent to propose a resolution for one pending hunk (ours/theirs/base + trace returned)gitwand_resolve_hunk_llmValidate an LLM-proposed resolution through the post-merge gate, then apply it to disk
MCP Gitlab tools 80
gitlab_get_projectGet project detailsgitlab_create_projectCreate a new projectgitlab_delete_projectDelete a projectgitlab_update_project_merge_settingsUpdate merge settingsgitlab_get_project_approvalsGet approval configgitlab_update_project_approvalsUpdate approval settingsgitlab_list_project_approval_rulesList approval rulesgitlab_create_project_approval_ruleCreate approval rulegitlab_update_project_approval_ruleUpdate approval rulegitlab_delete_project_approval_ruleDelete approval rulegitlab_list_mr_approval_rulesList MR approval rulesgitlab_create_mr_approval_ruleCreate MR approval rule- +68 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.
Gitwand
{
"mcpServers": {
"gitwand": {
"command": "npx",
"args": [
"-y",
"@gitwand/mcp"
]
}
}
}
MCP Gitlab
{
"mcpServers": {
"mcp-gitlab-2": {
"command": "uvx",
"args": [
"mcp-gitlab"
],
"env": {
"GITLAB_URL": "YOUR_GITLAB_URL_HERE",
"GITLAB_TOKEN": "YOUR_GITLAB_TOKEN_HERE",
"GITLAB_PAT": "YOUR_GITLAB_PAT_HERE",
"GITLAB_PERSONAL_ACCESS_TOKEN": "YOUR_GITLAB_PERSONAL_ACCESS_TOKEN_HERE",
"GITLAB_API_TOKEN": "YOUR_GITLAB_API_TOKEN_HERE",
"MCP_READ_ONLY": "YOUR_MCP_READ_ONLY_HERE",
"GITLAB_READ_ONLY": "YOUR_GITLAB_READ_ONLY_HERE",
"GITLAB_AUTH": "YOUR_GITLAB_AUTH_HERE"
}
}
}
}
Frequently asked questions
Gitwand is categorized under Version Control and uses a local stdio subprocess. MCP Gitlab belongs to Version Control and uses a local stdio subprocess. Pick Gitwand for version control work and MCP Gitlab 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.
Gitwand is listed as free. MCP Gitlab 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 gitwand and mcp-gitlab-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gitwand has a quality signal of 60/100 (Good) with 1 views, 0 installs and 186 GitHub stars. MCP Gitlab has 55/100 (Good) with 2 views, 0 installs and 6 GitHub stars.