---
title: "GitLab MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/gitlab/
description: "Connect a client to project, repository, review and CI context on GitLab.com or an enabled GitLab instance."
---

# GitLab MCP: review, setup & limitations · Undominated.ai

> Connect a client to project, repository, review and CI context on GitLab.com or an enabled GitLab instance.

[← Explore all mcp servers](/mcp-servers/)

REPOSITORY COLLABORATION / GitLab

# GitLab MCP

Connect a client to project, repository, review and CI context on GitLab.com or an enabled GitLab instance.

 [See setup guidance ↓](#setup)[Original source ↗](https://docs.gitlab.com/user/model_context_protocol/mcp_server/)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 2 linked sources
 Publisher GitLab
 Licence Not established
 [Read what was—and wasn’t—checked ↓](#review)

“Access GitLab project information.”

 [GitLab · upstream description ↗](https://docs.gitlab.com/user/model_context_protocol/mcp_server/) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - First-party OAuth exposes the GitLab resources the signed-in user may access.
- HTTP setup supports GitLab.com and supported self-managed or dedicated installations.
- GitLab’s MCP page says tools are listed only when the instance license includes the feature, and that listing a tool does not grant access.
- Each call still checks project and namespace permissions, and a pre-registered OAuth application is required where dynamic client registration is turned off.

### A good fit for

 - Investigate a GitLab project, merge request or CI workflow.
- Perform explicitly approved GitLab collaboration tasks.
- Calling GitLab from an MCP client as a user who already has the project permission the tool checks
- An instance that has turned off dynamic client registration and uses a pre-registered OAuth application

### Weigh up before choosing

 - The feature is currently beta and access must be enabled for the group or instance.
- Available tools can edit repository files, merge changes, and run or delete CI pipelines; actual tool availability depends on the instance and feature flags.
- OAuth client identity does not itself restrict which client software can authenticate.
- Listing a tool does not grant access, and users can access only data they are permitted to see.
- The merge-request conflict tool requires permission to push to the source branch and returns an error when there are no conflicts or mergeability has not been checked.
- No licence text was fetched. The pages were not used to change a licence.
- This review did not execute the resource.
- The server was not called.
- An api-scoped legacy PAT is not a substitute for an MCP-scoped token; a 403 can reflect token type rather than project visibility.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - Current GitLab MCP setup, enablement requirements, transport/authentication and toolset documentation.
- GitLab MCP tools reference.
- https://docs.gitlab.com/user/model_context_protocol/mcp_server/
- https://docs.gitlab.com/user/model_context_protocol/mcp_server_tools/
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

### Our findings

 - HTTP connects directly to /api/v4/mcp; mcp-remote is an optional stdio bridge, not the hosted server implementation.
- Toolset and individual-tool selection headers combine as a union. Existing user permissions still apply.
- GitLab documents an OAuth-based MCP server where every user still authorizes and receives their own access token. A shared application is the client identity, not a shared credential.
- Listing a tool does not grant access. Each tool checks project and namespace permissions, and users can access only data they are permitted to.
- Where an administrator turns off dynamic client registration, MCP clients cannot register applications automatically. One documented tool requires permission to push to the source branch of the merge request.
- The server accepts OAuth tokens with mcp scope or fine-grained PATs with MCP Execute permission; legacy/project/group access tokens are rejected.

### Not established by this review

 - Server launch, authenticated tool calls, and release-to-source parity were not tested.
- The resource was not executed and its tools were not called.
- The server was not called. A source review is not a runtime or security certification.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://docs.gitlab.com/user/model_context_protocol/mcp_server/)

DOCUMENTED COMMAND

 claude mcp add -s user --transport http GitLab https://<gitlab.example.com>/api/v4/mcp Copy command ↗

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

 - Enable MCP access for the GitLab.com group or self-managed instance.
- Replace <gitlab.example.com> with gitlab.com, or with your instance URL, as the page instructs. The -s user scope makes the server available in every project. The command was not run.
- Use /mcp in Claude Code to authorize GitLab, then inspect available tools and review mutations.

### Before you start

 - GitLab account with access to the relevant projects.
- MCP enabled by the group or instance administrator; an OAuth-capable client.

### Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

 {
 "mcpServers": {
 "GitLab": {
 "type": "http",
 "url": "https://<gitlab.example.com>/api/v4/mcp"
 }
 }
} Copy configuration ↗

### Compatibility

Claude Code · Cursor · VS Code · Codex

### Transports

HTTP

### Remote OAuth

 - Reads GitLab project/repository and collaboration data available to the user.
- Permitted tools can write repository files, create/update/merge requests, and change CI pipelines on the user’s behalf.

### Cost model

Availability follows the GitLab tier and instance settings; connected AI-client charges are separate.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [GitLab MCP setup and scope ↗](https://docs.gitlab.com/user/model_context_protocol/mcp_server/) Checked 2026-10-14 https://docs.gitlab.com/user/model_context_protocol/mcp_server/ Supports: summary, upstreamDescription, whySelected, bestFor, limitations, install, access, compatibility, transports, review
- [GitLab MCP tool reference ↗](https://docs.gitlab.com/user/model_context_protocol/mcp_server_tools/) Checked 2026-10-14 https://docs.gitlab.com/user/model_context_protocol/mcp_server_tools/ Supports: summary, whySelected, bestFor, access, review

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### GitHub MCP Server ↗ Connects an assistant to repository, issue, pull-request and workflow operations with selectable toolsets and account permissions.](/mcp-servers/github/)[### Git MCP reference server ↗ Inspect local Git history and diffs, then stage, commit, or switch branches through explicit tools.](/mcp-servers/git/)[### Gitee MCP Server ↗ Manage Gitee repositories, issues, pull requests and notifications with selectable tool groups.](/mcp-servers/gitee/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
