Gitlab MCP vs Gitlab MCP Server
A side-by-side look at the Gitlab MCP and Gitlab MCP Server 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 Gitlab MCP Server 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_PERSONAL_ACCESS_TOKEN_FILE, GITLAB_API_URL, GITLAB_USE_OAUTH, GITLAB_MCP_OAUTH, REMOTE_AUTHORIZATION, GITLAB_TOOLSETS, GITLAB_MCP_COMPACT_RESULTS. - You want tools like
mcp-remote, X-Gitlab-Enabled-Mcp-Server-Toolsets, X-Gitlab-Mcp-Server-Tool-Name-Prefix.
Choose Gitlab MCP Server when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
GITLAB_TOKEN, GITLAB_MCP_READ_ONLY. - You want tools like
gitlab_execute_action, gitlab_find_action.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 47/100 · Fair | 67/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | API key required | OAuth 2.0 |
| Pricing | Not declared | Free |
| Required env vars | GITLAB_PERSONAL_ACCESS_TOKENGITLAB_PERSONAL_ACCESS_TOKEN_FILEGITLAB_API_URLGITLAB_USE_OAUTHGITLAB_MCP_OAUTHREMOTE_AUTHORIZATIONGITLAB_TOOLSETSGITLAB_MCP_COMPACT_RESULTS | GITLAB_TOKENGITLAB_MCP_READ_ONLY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2,091 | 47 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 3 | 2 |
| Full listing | View Gitlab MCP | View Gitlab MCP Server |
Tools & capabilities
Gitlab MCP tools 3
mcp-remoteX-Gitlab-Enabled-Mcp-Server-ToolsetsX-Gitlab-Mcp-Server-Tool-Name-Prefix
Gitlab MCP Server tools 2
gitlab_execute_actionExecute one GitLab catalog action by canonical ID or alias. Always pass params as an object. Destructive actions require top-level confirm=true. Use find first only when action or params are unclear. Example: {"action":"issue.list","params":{"project_id":"group/project"}}gitlab_find_actionSearch the local GitLab action catalog. Read-only and no GitLab API call. Use when the action ID or params are unclear. Returns schemas, hints, destructive flags, and execute examples. Example: {"query":"issue list"}
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.
Gitlab MCP Server
{
"mcpServers": {
"jmrplens-gitlab-mcp-server": {
"command": "npx",
"args": [
"-y",
"@jmrp.io/gitlab-mcp-server"
],
"env": {
"GITLAB_TOKEN": "YOUR_GITLAB_TOKEN_HERE",
"GITLAB_MCP_READ_ONLY": "YOUR_GITLAB_MCP_READ_ONLY_HERE"
}
}
}
}
Frequently asked questions
Gitlab MCP is categorized under Version Control and uses an install path we have not confirmed yet. Gitlab MCP Server belongs to Version Control and uses a local stdio subprocess. Pick Gitlab MCP for version control work and Gitlab MCP Server 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. Gitlab MCP Server is listed as free. Auth: oauth 2.0. 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 jmrplens-gitlab-mcp-server 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,091 GitHub stars. Gitlab MCP Server has 67/100 (Great) with 3 views, 0 installs and 47 GitHub stars.