Log inSubmit server
Gitlab MCP logo

Gitlab MCP

Connects AI agents to GitLab for project, merge request, issue, pipeline, wiki, release, and related workflows.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Gitlab MCP

Pick your client, then add it in one click or paste the config.

No confirmed install command yet

We only publish a config when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for gitlab-mcp, and we’d rather show nothing than a guess you’d paste into your client.

Open setup steps on GitHub

Overview

gitlab-mcp connects AI clients to GitLab through 277 tools covering projects, merge requests, issues, pipelines, wikis, releases, tags, milestones, and more. It runs locally over stdio or remotely through SSE and Streamable HTTP, with support for GitLab.com and custom GitLab instances. Reach for it when an agent needs to inspect or manage GitLab work, review merge request changes, or query GitLab through GraphQL. Authentication can use a personal access token, OAuth2, an MCP OAuth proxy, or per-request remote authorization.

Use cases

  • Review merge request changes and retrieve batched file diffs
  • Inspect project issues, pipelines, releases, and milestones
  • Manage GitLab wiki pages, tags, and project workflows
  • Query GitLab through GraphQL from an AI agent
  • Connect agents to self-hosted GitLab instances

Key features

  • 277 GitLab tools with runtime tool discovery
  • Merge request changed-file and batched-diff workflow
  • Stdio, SSE, and Streamable HTTP transports
  • Personal access token and OAuth-based authentication
  • Read-only mode and custom GitLab API URLs
  • Optional JMESPath result filtering

Tools3

What Gitlab MCP lets your agent do. Expand a tool for its parameters.

Self-reported~21 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

12/12 checks healthy over the last 45d

Supply-chain signal

4 high-severity advisories on record for this package. Most advisories affect transitive dependencies and may not be exploitable in this server's actual usage — this is a directional signal, not a security audit.

Critical 3High 1Medium 0Low 0

Scanned 6d ago via OSV.dev

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2.1kStargazers on the source repository.
Last commitTodayMost recent push to the default branch.
Tools exposed3Callable tools this server registers over MCP.

How Gitlab MCP works

What gitlab-mcp does

gitlab-mcp exposes GitLab operations to MCP-compatible AI clients. Its coverage includes projects, merge requests, issues, pipelines, wiki content, releases, tags, and milestones. The package provides 277 tools in total: 275 organized into toolsets, plus execute_graphql and discover_tools.

The server is aimed at agent workflows that need to retrieve GitLab data, carry out GitLab changes, or follow structured review processes. A built-in Agent Skill supplies workflow guidance, and merge request review can use a two-stage process: first identify changed files, then request file diffs in batches.

How it works

Local clients can launch the zereight-mcp-gitlab binary over stdio. Remote deployments can use SSE for older clients or Streamable HTTP for newer remote MCP clients. The server can target GitLab.com or a self-hosted GitLab installation through a configurable API URL, with proxy support and dynamic API URL routing.

Authentication options include a personal access token, a local OAuth2 browser flow, an MCP OAuth proxy, and authorization supplied for individual remote requests. Read-only mode is available when agents should inspect GitLab without making changes.

Toolsets keep the initial tool selection smaller. Additional tools can be activated at runtime with discover_tools, while execute_graphql provides a direct GraphQL capability. Tool calls can optionally apply JMESPath filtering to reduce returned JSON without changing the underlying GitLab API request.

Setup and configuration

Install the npm package globally with npm install -g @zereight/mcp-gitlab, or install the binary through Homebrew using the zereight/gitlab-mcp tap. The executable is named zereight-mcp-gitlab.

A typical local configuration supplies GITLAB_PERSONAL_ACCESS_TOKEN and sets GITLAB_API_URL to https://gitlab.com/api/v4. Claude Code and Codex can register the server with their MCP commands; Cursor and VS Code provide client-specific setup paths. JSON-based MCP clients can configure the same stdio command and environment variables.

The package requires Node.js 18.17 or newer. Custom GitLab servers should use their own API v4 endpoint in GITLAB_API_URL.

Tools and capabilities

  • Manage and inspect GitLab projects.
  • Work with merge requests, including changed-file discovery and batched file diffs.
  • Read and manage issues, pipelines, wiki content, releases, tags, and milestones.
  • Execute GraphQL requests through execute_graphql.
  • Discover and activate additional tools at runtime with discover_tools.
  • Filter tool results with optional JMESPath expressions.

The server supports Claude Code, Codex, Cursor, VS Code, Cline, Roo Code, and other MCP clients that can run stdio or connect through its remote transports.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Gitlab MCP

gitlab-mcp is an MCP server that connects AI clients to GitLab through tools for projects, merge requests, issues, pipelines, wikis, releases, tags, and milestones. It also provides `execute_graphql` for GraphQL requests and `discover_tools` for activating additional tools at runtime.

Install it with `npm install -g @zereight/mcp-gitlab` or through Homebrew using the `zereight/gitlab-mcp` tap. Then configure your MCP client to launch `zereight-mcp-gitlab` and provide the GitLab token and API URL.

Set `GITLAB_PERSONAL_ACCESS_TOKEN` for token authentication and `GITLAB_API_URL` to the GitLab API v4 endpoint, such as `https://gitlab.com/api/v4`. Custom GitLab instances should use their corresponding API URL.

Yes. gitlab-mcp includes a Cursor setup path and runs through the standard stdio transport. Configure the package command with `GITLAB_PERSONAL_ACCESS_TOKEN` and `GITLAB_API_URL` in Cursor's MCP settings.

Yes. Set `GITLAB_API_URL` to the API v4 endpoint for the self-hosted instance. The server also supports proxy settings and dynamic API URL routing for custom GitLab deployments.

Related MCP servers

All in Version Control All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGitlab MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/gitlab-mcp?style=directory)](https://allmcps.com/mcp/gitlab-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/gitlab-mcp"><img src="https://allmcps.com/api/badge/gitlab-mcp?style=directory" alt="Gitlab MCP on AllMCPs" /></a>