MCP Radar

GitLab MCP Server

The GitLab MCP Server covers most of what you do in GitLab day to day: reading and writing issues and merge requests, checking CI pipeline status and logs, browsing repo files, and posting comments.

It's most useful for CI triage — ask "why did the last pipeline fail?" and the AI pulls the logs and pinpoints the failing job and error line, instead of you clicking down through the GitLab UI.

See this server's health data →

Install / Connect

# No npm package — install from source.
# See the repo's README for the exact command:
# https://github.com/zereight/gitlab-mcp

Follow the official README; env and args vary per server.

Why use it

Good for: teams on GitLab rather than GitHub — the GitHub ecosystem is crowded, GitLab's is thin, and this is one of the most-adopted community implementations.

Before connecting: you'll need a GitLab Personal Access Token. Scope it to what you need — read_api is enough for read-only use; don't hand over full api scope by default.

Similar / alternative servers

Frequently Asked Questions

Does it work with self-hosted GitLab?

Yes. Point the config at your instance URL — both gitlab.com and self-hosted work.

Can it create merge requests?

It can create MRs, write descriptions, and add comments. Decide whether you want write scope when you issue the token.