--- 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 ↓Original source ↗ SOURCE REVIEW Reviewed 2026-09-21 Evidence 2 linked sources Publisher GitLab Licence Not established Read what was—and wasn’t—checked ↓ “Access GitLab project information.” GitLab · upstream description ↗ 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. ### A good fit for - Investigate a GitLab project, merge request or CI workflow. - Perform explicitly approved GitLab collaboration tasks. ### 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. 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. ### 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. ### Not established by this review - Server launch, authenticated tool calls, and release-to-source parity were not tested. 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 ↗ DOCUMENTED COMMAND claude mcp add --transport http GitLab https://gitlab.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. - The command below configures Claude Code for GitLab.com; replace the hostname for your own enabled instance. - 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.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 ↗ Checked 2026-09-21 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 ↗ Checked 2026-09-21 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/)[### Vercel MCP ↗ Search Vercel docs, inspect projects and runtime failures, and deploy a supplied file tree through the hosted endpoint.](/mcp-servers/vercel/) [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)