GitLab MCP Server: Issues, MRs and CI in Claude Code
GitLab's built-in MCP server lets Claude read projects, issues, merge requests and CI pipelines on GitLab.com or self-managed. Claude Code setup, toolsets.
By Claudekit Team Published 2 min read
- Type
- MCP Server
- Pricing
- Freemium
- Repository
- gitlab.com
- Website
- docs.gitlab.com
The GitLab MCP server is built into GitLab itself, so there is nothing to install or host. It lets Claude read project information, issues, work items, merge requests, repository content and CI pipelines, and act on them with your GitLab permissions. It works on GitLab.com, GitLab Self-Managed and GitLab Dedicated.
Who it is for
Teams that host code on GitLab and want Claude Code to pick up an issue, review a merge request or check why a pipeline failed, without switching to the browser.
Install
First, make sure access to the MCP server is allowed for your top-level group (GitLab.com) or instance (self-managed). Then use the command from GitLab’s docs. Replace <gitlab.example.com> with gitlab.com or your instance URL:
claude mcp add -s user --transport http GitLab https://<gitlab.example.com>/api/v4/mcp
Start claude, type /mcp, select GitLab and approve the OAuth request in your browser. Claude Code registers itself through OAuth dynamic client registration, so you do not paste a token. To load only some toolsets:
claude mcp add -s user --transport http GitLab https://<gitlab.example.com>/api/v4/mcp \
--header "X-Gitlab-Enabled-Mcp-Server-Toolsets: core,work_items"
Use cases
- Issue to code: “Read issue 42 in this project and propose a fix.”
- MR review: summarize a merge request’s changes and open discussions.
- CI triage: find the failed job in the latest pipeline and explain the error.
- Work items: list open work items assigned to you this milestone.
Pros
- Official and built into GitLab, available on the Free tier.
- OAuth with dynamic client registration, so no long-lived token in your config.
- Toolsets and tool-name prefixes keep large setups manageable.
- Same server for GitLab.com and self-managed instances.
Cons and caveats
- An admin must allow MCP access first.
- Legacy personal, project and group access tokens are rejected.
- Some toolsets need paid features: Duo Agent Platform tools need Duo access, and code security tools need Ultimate features.
- GitLab warns that you are responsible for guarding against prompt injection. Use the tools only on GitLab objects you trust.
Links
- Docs: GitLab MCP server
- Related: GitHub MCP server, Linear MCP, Atlassian MCP server
Checked 24 Oct 2026 against the GitLab docs source and the MCP registry.
Frequently asked questions
Which GitLab tiers include the MCP server?
GitLab's docs list Free, Premium and Ultimate on GitLab.com, Self-Managed and Dedicated. It moved from Premium to Free in GitLab 19.2 and became generally available in 19.5.
Why does my personal access token get 403 Forbidden?
The server needs an OAuth token with the mcp scope or a fine-grained personal access token with the MCP tool resource. Legacy personal, project and group access tokens are rejected.
How do I limit which tools Claude sees?
Send the X-Gitlab-Enabled-Mcp-Server-Toolsets header with a comma-separated list such as core,work_items. Wikis, code_security and orbit are opt-in.
Does an admin need to enable it?
Yes. Access must be allowed for the top-level group on GitLab.com, or for the instance on Self-Managed and Dedicated.