gitlab-mcp
gitlab-mcp is an MCP server published by zereight, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. It is a community implementation. Last verified 2026-08-20.
Does gitlab-mcp support the current MCP specification (2026-07-28)?
Not yet confirmed. gitlab-mcp is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is gitlab-mcp a first-party (official) MCP server?
No. gitlab-mcp is a community-published MCP server from zereight, not a first-party vendor server (last verified 2026-08-20).
How do I connect to gitlab-mcp?
gitlab-mcp is available via the package npm:@zereight/mcp-gitlab, the official MCP Registry under io.github.zereight/gitlab-mcp, the source repository at https://github.com/zereight/gitlab-mcp. Authentication: none. Transports: stdio, streamable-http, sse-legacy.
Does gitlab-mcp support MCP revision 2025-11-25?
Yes. gitlab-mcp supports MCP revision 2025-11-25 (checked 2026-08-20).
Does gitlab-mcp support MCP revision 2026-07-28?
No. gitlab-mcp was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were gitlab-mcp's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
gitlab-mcp is a community MCP server for the GitLab API, maintained by the independent developer zereight (a personal GitHub account based in Seoul, unaffiliated with GitLab). It covers projects, merge requests, issues, pipelines, wiki, releases, tags, and milestones, and speaks three transports: stdio for local clients, streamable HTTP for remote deployments, and legacy SSE. The default setup needs a GitLab personal access token; self-hosted remote modes add OAuth flows, including a proxy mode for clients like Claude.ai and a multi-user mode where each caller supplies its own token.
Do not confuse it with GitLab's own product: GitLab operates an official MCP server, documented on docs.gitlab.com, which states support for the 2025-03-26 and 2025-06-18 revisions arriving in GitLab 18.7. The community server predates it and remains very actively maintained, with five releases in the last two weeks of this verification window; v2.1.43 fixed four published GitHub security advisories.
No surface names a supported MCP specification revision for gitlab-mcp
itself. A changelog entry cites the 2025-06-18 spec's transport section
to justify one HTTP behavior, which documents a feature reference, and
the @modelcontextprotocol/sdk ^1.29.0 dependency is not evidence.
spec_status is therefore unknown.
Which MCP spec revisions does gitlab-mcp support?
gitlab-mcp 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-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is gitlab-mcp?
Ranked #15 in The MCP 500 with Adoption Index 69.73 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 82,103 | API · |
| GitHub stars | 1,976 | API · |
| GitHub forks | 357 | API · |
| Last push | 2026-09-15T13:57:25Z | API · |
| Repository archived | no | API · |
Repository and package signals for gitlab-mcp
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Created
- Open issues
- 12
- Primary language
- TypeScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- Present
- Security policy
- None
Package (npm) as of
- Latest version
2.1.52- Last published
- First published
- Releases
- 147
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 19
- Unpacked size
- 2.0 MB
- Registry signature
- Signed
- Build provenance
- Attested
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record io.github.zereight/gitlab-mcp version 2.1.46 (published 2026-08-02) - npm package @zereight/mcp-gitlab, stdio transport; the package's server.json marks GITLAB_PERSONAL_ACCESS_TOKEN as required - accessed
- zereight/gitlab-mcp README - "A comprehensive GitLab MCP server for AI clients. Manage projects, merge requests, issues, pipelines, wiki, releases, tags, milestones, and more through stdio, SSE, and Streamable HTTP"; four auth methods documented: personal access token, a local OAuth2 browser flow, an OAuth2 MCP proxy mode for remote clients, and a multi-user remote-authorization mode; owner is the personal account zereight with no GitLab affiliation stated - accessed
- gitlab-mcp releases - v2.1.46 (2026-08-02); v2.1.43 (2026-07-26) fixed four GitHub security advisories (GHSA-2h44-8472-frjj, GHSA-cv3r-c5h8-f4g5, GHSA-4rm9-rfp2-j39q, GHSA-5648-rgj9-v224); five releases shipped in the two weeks before this check - accessed
- GitLab docs "MCP server" - GitLab's own, separate official MCP server: "GitLab provides an official Model Context Protocol server", with support for spec revisions 2025-03-26 and 2025-06-18 added in GitLab 18.7; cited here to distinguish the two products - accessed
- Staleness re-verification 2026-08-18 - official registry record io.github.zereight/gitlab-mcp is at v2.1.49 (published 2026-08-18, status active), npm package @zereight/mcp-gitlab 2.1.49, no remote endpoints listed; the repository is not archived and was pushed 2026-08-18 - accessed
- npm registry metadata for @zereight/mcp-gitlab at published version 2.1.49, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed