Gitlab MCP vs MCP Gitlab
A side-by-side look at the Gitlab MCP 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 Gitlab MCP for version control work; 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 Gitlab MCP when
- You need dedicated capabilities in the Version Control domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
GITLAB_PERSONAL_ACCESS_TOKEN, GITLAB_API_URL. - You want tools like
mcp-remote, X-Gitlab-Enabled-Mcp-Server-Toolsets, X-Gitlab-Mcp-Server-Tool-Name-Prefix.
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 | 47/100 · Fair | 55/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | GITLAB_PERSONAL_ACCESS_TOKENGITLAB_API_URL | GITLAB_URLGITLAB_TOKENGITLAB_PATGITLAB_PERSONAL_ACCESS_TOKENGITLAB_API_TOKENMCP_READ_ONLYGITLAB_READ_ONLYGITLAB_AUTH |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,062 | 6 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | 80 |
| Full listing | View Gitlab MCP | View MCP Gitlab |
Tools & capabilities
Gitlab MCP tools 3
mcp-remoteX-Gitlab-Enabled-Mcp-Server-ToolsetsX-Gitlab-Mcp-Server-Tool-Name-Prefix
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.
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.
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
Gitlab MCP is categorized under Version Control and uses an install path we have not confirmed yet. MCP Gitlab belongs to Version Control and uses a local stdio subprocess. Pick Gitlab MCP 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. 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. Auth: api key required. 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 gitlab-mcp and mcp-gitlab-2 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 47/100 (Fair) with 0 views, 0 installs and 2,062 GitHub stars. MCP Gitlab has 55/100 (Good) with 1 views, 0 installs and 6 GitHub stars.