Gitlab MCP vs Git MCP
A side-by-side look at the Gitlab MCP and Git MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gitlab MCP for version control work; choose Git 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 Gitlab MCP when
- You need dedicated capabilities in the Version Control domain.
- You want tools like
get_me, resolve_url, search_projects.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 45/100 · Fair | 49/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 8,472 |
| Directory activity | 2 views 0 installs 0 upvotes | 7 views 0 installs 0 upvotes |
| Tools | 80 | Not listed |
| Full listing | View Gitlab MCP | View Git MCP |
Tools & capabilities
Gitlab MCP tools 80
get_meWho is signed in, with which scopes, and what GitLab reports about itselfresolve_urlTurn a GitLab web URL into the arguments another tool takes, and name that toolsearch_projectsFind projects by name, or within a groupget_projectOne project: default branch, visibility, what it has turned onlist_membersWho has access to a project, and with which rolefind_usersAccounts by exact username or by namesearch_issuesFind issues across gitlab.com, a group or a projectget_issueOne issue, its description marked as untrusted content, and its linked merge requestscreate_issueCreate an issue; labels, assignees and milestone checked firstupdate_issueChange an issue's fields, refused if it changed since you read itlist_discussionsThe comment threads on an issue or a merge requestlist_item_eventsAn issue's or a merge request's label, state, milestone and weight changes, newest first- +68 more on the listing page
Git MCP 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.
Gitlab MCP
No confirmed install command for Gitlab MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Git MCP
{
"mcpServers": {
"idosal-git-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote"
]
}
}
}
Frequently asked questions
Gitlab MCP is categorized under Version Control and uses an install path we have not confirmed yet. Git MCP belongs to Version Control and uses a local stdio subprocess. Pick Gitlab MCP for version control work and Git 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. Gitlab MCP has no confirmed install command yet — follow its own setup instructions.
Gitlab MCP has no declared pricing — check the project's own site. Git MCP 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 gitlab-mcp-2 and idosal-git-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gitlab MCP has a quality signal of 45/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Git MCP has 49/100 (Fair) with 7 views, 0 installs and 8,472 GitHub stars.