Official (Vendor)★ 4.3by GitLab

GitLab

GitLab's hosted MCP server, built into GitLab 18.6+. Manage MRs, browse repos, work with CI pipelines from Claude.

View repo Homepage

Safety & Trust

Delv Safety Grade: A

Score 84/100 · assessed 2026-04-28

Maintainer95

Permissions75

Supply chain65

Transparency90

Incidents100

GitLab's official MCP server is first-party code from a major DevOps platform vendor, which provides strong maintainer legitimacy and API alignment. The server is built directly into GitLab 18.6+ as a hosted service, eliminating traditional supply chain concerns around npm packages or third-party distributions. Permissions are moderately scoped: it can read repositories, write merge request comments, and manage CI pipelines, but all actions are constrained to GitLab's API surface. The main supply chain consideration is that it's a hosted service requiring a personal access token rather than a locally installed package, which means you're trusting GitLab's infrastructure. Documentation is comprehensive and the codebase is fully open source within GitLab's main repository. No known security incidents. The token-based auth model is standard for GitLab integrations but does grant broad access depending on token scope.

Lethal Trifecta (prompt-injection exposure)

TRIFECTA RISK

All three axes present. This server can read private data, ingest attacker-controlled content, and send data outbound. A poisoned input (a GitHub issue, an email, a webpage) can exfiltrate secrets via this chain. Only install with auditing; avoid on shared or cloud agents.

Private dataYes

Reads secrets, credentials, private files

Untrusted inputYes

Ingests web pages, PRs, issues, emails

External commsYes

Can send data outbound

Same shape as the GitHub server. Issues and merge-request bodies are attacker-controlled; pipelines and tokens give outbound.

Green flags

Official first-party code from GitLab, major established vendor
Built into GitLab 18.6+, tracks platform API without lag
Fully open source in main GitLab repository with active maintenance
Comprehensive official documentation and changelog
No known security incidents or credential leaks

Red flags

Personal access token grants broad GitLab permissions based on scope selected
Hosted service means trusting GitLab's infrastructure for MCP execution
No package distribution means harder to audit specific MCP server code
Token compromise could allow repo writes, pipeline triggers, MR manipulation

Permissions requested

Repo readRepo writeOutbound networkAccess secretsSend messages

Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Review

GitLab's official MCP server brings merge request workflows, repository browsing, and CI pipeline management directly into Claude. This is first-party code from GitLab themselves, which means it tracks the platform's API properly and doesn't lag behind on features. You can review MRs, comment on diffs, check pipeline status, and browse project files without leaving your editor or Claude Desktop. I'd reach for this when triaging MRs across multiple repos or when debugging CI failures that need context from code and logs. The ability to ask Claude to summarise a diff, suggest review comments, or explain why a pipeline failed is genuinely useful. You can also create branches and push commits, though I find myself doing that less often through the MCP than through git directly. The main quirk is that it requires a personal access token with fairly broad permissions. You'll need to create one in GitLab's settings with API scope, which feels heavier than some other MCPs. The token lives in your environment variables, so rotation means updating your config and restarting your host. There's no OAuth flow here. Another thing to watch: if you work across self-hosted GitLab instances and GitLab.com, you'll need separate tokens and potentially separate MCP configurations. The server doesn't handle multi-instance setups elegantly out of the box. Performance is fine for small to medium repos, but asking Claude to summarise a 50-file MR can take a few seconds while it fetches everything. Who shouldn't bother: if you rarely touch GitLab or only work on solo projects, this won't change your life. It shines when you're juggling multiple MRs, reviewing code from teammates, or debugging CI in repos you don't know well. If you're a GitHub-only shop, obviously skip it. If you're already happy with GitLab's web UI and don't see the appeal of LLM-assisted code review, this won't convert you.

Verdict

Install this if you spend serious time reviewing GitLab MRs or debugging pipelines. The first-party support means it works reliably, and the CI integration is better than cobbling together API calls yourself. Skip it if you're a casual GitLab user or work solo.

Good at

First-party GitLab code means reliable API coverage and timely updates.
CI pipeline integration lets you debug failures without leaving Claude.
MR review workflows feel natural when combined with Claude's code understanding.
Works across GitLab.com and self-hosted instances with the right token.

Watch out

Requires a personal access token with broad API scope, which feels heavy for what it does.
No OAuth flow, so token rotation means manual config updates and restarts.
Multi-instance setups need separate configurations or token swapping.
Large MRs with many files can take several seconds to fetch and summarise.

Getting started

1. Generate a personal access token in GitLab (Settings > Access Tokens) with 'api' scope. Store it securely. 2. Add the token to your environment as GITLAB_PERSONAL_ACCESS_TOKEN. On macOS, edit ~/.zshrc or ~/.bash_profile and export it there. 3. Add the MCP server to your Claude Desktop config at ~/Library/Application Support/Claude/claude_desktop_config.json. Point the command at the GitLab MCP server path and pass the token via env. 4. Restart Claude Desktop. Test by asking Claude to list your recent GitLab projects or fetch a specific MR. 5. Watch out: if you work across multiple GitLab instances, you'll need to configure separate servers or swap tokens manually.

Works with

Claude DesktopClaude CodeCursorWindsurfClineZed