GitLab's Official MCP Server: From Experimental to Beta

GitLab runs its own official MCP server, documented at docs.gitlab.com/user/model_context_protocol/mcp_server/. It was introduced as an experimental feature in GitLab 18.3 and promoted to Beta in GitLab 18.6 — real, shipping, versioned progress rather than a permanent experiment.

What It Connects

The official server lets AI tools (Claude Desktop/Code, Cursor, and other MCP clients) securely connect to a GitLab instance and interact with projects, repositories, issues, merge requests, and CI/CD pipelines using natural language — positioned by GitLab as making AI assistants genuine "intelligent DevOps collaborators" rather than just code-completion tools.

OAuth 2.0 Dynamic Client Registration

A notable technical detail: GitLab's server supports OAuth 2.0 Dynamic Client Registration, which lets AI tools register themselves with a GitLab instance programmatically rather than requiring a pre-configured OAuth app for every client — meaningfully lowering the setup friction compared to a manual app-registration step per tool.

Protocol Version Support Is Actively Moving

GitLab added support for the 2025-03-26 and 2025-06-18 MCP protocol specification versions in GitLab 18.7 — worth knowing if you're troubleshooting a client compatibility issue, since which spec version your GitLab instance and your MCP client both support can matter for feature availability.

If You're Building a Narrower Custom Integration

For a purpose-built tool set beyond what the official server models — say, a single tool combining merge-request diff stats with your team's specific review-policy check — a minimal custom server against GitLab's REST/GraphQL API is still reasonable. Whichever path you take, scope access tokens to api only for the specific projects the agent needs, avoiding personal tokens with instance-wide access.