GitLab's own MCP server — issues, merge requests, CI/CD pipelines, job logs, wikis and semantic code search over an OAuth-authorised HTTP endpoint.
GitLab MCP (zereight)
Summary
Community GitLab MCP server with 288 tools for merge requests, issues, pipelines, wikis and releases — a lean 40-tool default that agents expand on demand, for gitlab.com or self-managed instances.
Features
- 288 tools for projects, merge requests, issues, pipelines, wikis, releases and milestones
- Lean 40-tool default with discover_tools to activate more per session
- Two-step merge-request review and paginated pipeline job logs
- PAT, local OAuth, MCP OAuth for Claude.ai and per-request remote authorization
- stdio, SSE and Streamable HTTP; works with self-managed GitLab
Installation
Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.
Description
@zereight/mcp-gitlab is the most widely used community MCP server for GitLab, and it takes a different route from GitLab's own built-in server: it runs as a separate process against the GitLab REST and GraphQL APIs, authenticates with a personal access token, local OAuth or per-request remote authorization, and works with gitlab.com and self-managed instances alike, including behind proxies.
Many tools, small footprint. 288 tools exist across projects, merge requests, issues, pipelines and job logs, wikis, releases, tags and milestones, but the default exposes only 40 — 38 core tools plus discover_tools and help, about 12k tokens of schema. An agent calls discover_tools to switch on another category for the session instead of paying for every schema up front; the README measures GITLAB_TOOLSETS=all at roughly 73k tokens and advises against it. Any call can take a jmespath expression to shrink its JSON result.
Built around review work. Merge-request review is a two-step flow — list the changed files, then fetch batched per-file diffs — and pipeline job output is paginated, so an agent can read a failing log without flooding its context. An optional api toolset exposes a raw gitlab_api_request, which the README flags as dangerous because it bypasses allowlists and per-tool safety checks.
It speaks stdio, SSE and Streamable HTTP; supports read-only mode, dynamic API URLs and stateless multi-pod deployment; and can serve Claude.ai through an MCP OAuth proxy. The same package ships a zereight-mcp-gitlab CLI and an agent skill as a non-MCP alternative. Install from npm or Homebrew. MIT-licensed.
Related MCP Servers
See all GitLab MCP (zereight) alternativesMCP: Buildkite MCP Server
by Buildkite
Buildkite's official MCP server: query pipelines, builds, jobs, logs, test runs and flaky-test data from an agent, over a hosted OAuth endpoint or a self-run binary.
MCP: CircleCI MCP Server
by CircleCI
CircleCI's official MCP server: pull build failure logs, hunt flaky tests, validate config, trigger and rerun pipelines, and roll back - in natural language from your IDE.
MCP: Argo CD MCP Server
by argoproj-labs
Argo CD's MCP server from argoproj-labs — list and sync applications, walk the resource tree and read workload logs in natural language.