GitLab MCP Server
GitLab's built-in MCP server connecting external agents to projects, issues, merge requests, pipelines and work items. Generally available since GitLab 19.5 across all editions including Self-Managed and Dedicated.
- Website
- https://docs.gitlab.com/user/model_context_protocol/mcp_server/
- Who it's for
- Teams on GitLab.com, Self-Managed or Dedicated who want agents to run GitLab workflows under existing user permissions.
- Pricing
- Included with all GitLab tiers at no extra cost. On GitLab.com, rate limits are 60 calls/min on Free and 600 on Premium/Ultimate.
- Category
- MCP servers & connectors
- Last verified
- 2026-10-22 (current)
- Confidence
- high
Key facts
- Transport: HTTP at the instance API MCP path (recommended); stdio via the mcp-remote proxy
- Auth: OAuth 2.0 Dynamic Client Registration; actions run under the connected user's permissions
- Covers repositories, issues, merge requests, pipelines and work items
- Generally available across GitLab.com, Self-Managed and Dedicated
Sources
Every claim above is drawn from these; we do not publish unsourced specifications.
- https://docs.gitlab.com/user/model_context_protocol/mcp_server/
- https://about.gitlab.com/blog/mcp-server-ga/
Something changed or out of date? Tell us — corrections are how this stays worth reading.