GitLab MCP Server
Earlier Revision Confidence: High (0.90)GitLab MCP Server is an MCP server published by GitLab, verified on MCP revision 2025-06-18; support for the current revision (2026-07-28) is not yet confirmed. It is the first-party server from GitLab. Last verified 2026-08-14.
Does GitLab MCP Server support the current MCP specification (2026-07-28)?
Not yet confirmed. GitLab MCP Server is verified on revision 2025-06-18; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-14.
Is GitLab MCP Server a first-party (official) MCP server?
Yes. GitLab MCP Server is the first-party MCP server published by GitLab (last verified 2026-08-14).
How do I connect to GitLab MCP Server?
GitLab MCP Server is available via a hosted remote endpoint at https://gitlab.com/api/v4/mcp, the official MCP Registry under com.gitlab/mcp, the source repository at https://gitlab.com/gitlab-org/gitlab. Authentication: oauth. Transports: streamable-http.
Does GitLab MCP Server support MCP revision 2025-06-18?
Yes. GitLab MCP Server supports MCP revision 2025-06-18 (checked 2026-08-14).
Does GitLab MCP Server support MCP revision 2025-03-26?
Yes. GitLab MCP Server supports MCP revision 2025-03-26 (checked 2026-08-14).
When were GitLab MCP Server's facts last verified?
2026-08-14. Each fact on this page links to the sources used to verify it.
The GitLab MCP Server is GitLab's official server, built into the
GitLab application rather than shipped as a separate package: every
GitLab.com, Self-Managed, or Dedicated instance exposes it at
/api/v4/mcp. It entered as an experiment in GitLab 18.3, became beta
in 18.6, and moved from the Premium to the Free tier in 19.2, so it is
available in beta on all tiers.
Spec support is documented but trails the current revision: GitLab's docs state that support for the 2025-03-26 and 2025-06-18 protocol specifications was added in GitLab 18.7, and no GitLab surface names the 2026-07-28 revision. A probe of the gitlab.com endpoint on 2026-08-14 returned a genuine OAuth bearer challenge pointing at GitLab's protected-resource metadata, which grounds the authentication model (OAuth 2.0 with Dynamic Client Registration per the docs) but leaves revision behavior unobservable without credentials.
The registry record under the DNS-verified com.gitlab namespace is minimal (v0.0.1, published 2025-10-02) and lists the remote endpoint and the gitlab-org/gitlab repository, where the server's implementation lives in the main GitLab codebase.
Which MCP spec revisions does GitLab MCP Server support?
GitLab MCP Server has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-06-18 | Supported | Source | |
| MCP 2025-03-26 | Supported | Source |
How widely adopted is GitLab MCP Server?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
How was this verified, and what are the sources?
Verified · method: vendor-docs
· confidence 0.90 (High).
- GitLab documentation "GitLab MCP server" - endpoint https://<gitlab.example.com>/api/v4/mcp; "Support for 2025-03-26 and 2025-06-18 MCP protocol specifications added in GitLab 18.7"; introduced as an experiment in GitLab 18.3, beta since 18.6, moved from Premium to Free tier in 19.2; OAuth 2.0 Dynamic Client Registration; beta on GitLab.com, Self-Managed, and Dedicated; supports the X-Gitlab-Mcp-Server-Tool-Name-Prefix header - accessed
- Official MCP Registry record com.gitlab/mcp v0.0.1 - "Official GitLab MCP Server", DNS-verified com.gitlab namespace, remote streamable-http https://gitlab.com/api/v4/mcp, repository gitlab.com/gitlab-org/gitlab, published 2025-10-02 - accessed
- Endpoint probe of https://gitlab.com/api/v4/mcp - server/discover POST at 2026-07-28 returned HTTP 401 with WWW-Authenticate Bearer realm="GitLab" and resource_metadata https://gitlab.com/.well-known/oauth-protected-resource/api/v4/mcp; capability set not observable without credentials - accessed