GitLab MCP Server
Community GitLab MCP server — MRs, issues, pipelines as agent tools.
About
A community GitLab MCP server (zereight/gitlab-mcp, MIT, ~2k stars): merge requests, issues, pipelines, and repo operations as agent tools.
Very actively maintained (97 releases/12mo) with a clean issue record. Caveat: it is unofficial — if GitLab ships its own MCP server, prefer that. Until then, this is the practical option for GitLab shops.
What it can do
- MRs, issues, pipelines
- Repo operations
- MIT open source
- Very active maintenance
- Unofficial (community)
Setup
- Create a GitLab personal access token.
- Add the server to your MCP config with your GitLab URL and token.
Prerequisites
GitLab instance; personal access token.
Use cases
Works with
Trust score — 8/10
Scored 8/10 (verified tier). MIT, very actively maintained with a clean issue record. Docked for being unofficial (community, not GitLab). Verified tier on health.
★ 2,034 GitHub stars
How the trust score is built
Full methodology →- Adoption · stars/downloads, log-scaled vs peers
- 6.4/10
- Maintenance · recency, releases, issue load
- 9.7/10
- Openness · license + docs
- 9.1/10
- Manual review · sanity read + red-flag check
- 7.0/10
- · 2,034 GitHub stars (log-scaled vs catalog peers)
- · last push 1d ago; 97 releases/12mo; 17 open issues
- · manual review: community GitLab MCP server (zereight); active; unofficial — check GitLab's own if one ships; license: MIT
Sources
Every fact above was checked against these sources. Where a claim comes from the provider and couldn't be independently verified, the text says so.