GitLab MCP Server
Work with GitLab merge requests, work items, pipelines and code from Claude.
Officialby GitLabHosted, nothing to installChecked October 18, 2026
GitLab's built-in MCP server, generally available since GitLab 19.5, lets Claude read and update merge requests, work items, repository files and CI/CD pipelines on GitLab.com, Self-Managed or Dedicated. It runs inside GitLab itself, so you sign in with OAuth and Claude acts with your own access.
Who it is for
- Teams that host code on GitLab
- Developers reviewing merge requests
- Platform teams chasing pipeline failures
Prompts to try
Once it is connected, ask in plain words. Claude decides when to use the server and asks before it changes anything important.
List the merge requests waiting for my review in the web-app project and summarize each one.Why did the latest pipeline on main fail? Show the failing job and its error.Create a work item for the broken password reset email and link it to merge request 42.How to connect it
In Claude Code
claude mcp add -s user --transport http GitLab https://gitlab.com/api/v4/mcp
In the Claude desktop app
Customize > Connectors > + Add > Add custom connector, URL: https://gitlab.com/api/v4/mcp
Hosted address: https://gitlab.com/api/v4/mcp
Good to know
A top-level group owner (or an instance admin on Self-Managed and Dedicated) must allow MCP access first; self-hosted instances use https://YOUR_GITLAB_HOST/api/v4/mcp.
Unlock the setup steps
Free. Leave your email once to open the setup steps for all 150 servers, and get the best new connectors each month.
How we checked it
Checked GitLab's MCP server docs and tools page, the GitLab 19.5 release notes (general availability, released 2026-10-15) and the registry entry com.gitlab/mcp; the gitlab.com endpoint answers with an OAuth challenge.
Source: docs.gitlab.com/user/model_context_protocol/mcp_server/