@zereight/mcp-gitlab weekly downloads statistics

GitLab MCP Server

English | 한국어 | 简体中文 | Português (Brasil)

📖 Documentation → Setup guides, environment variables, and the full tool reference live on the hosted docs site.

Install @zereight/mcp-gitlab with the recommended local personal-access-token setup. These commands use the same arguments as the Claude Code and Codex guides.

Install the zereight-mcp-gitlab binary first with npm install -g @zereight/mcp-gitlab, or Homebrew brew tap zereight/gitlab-mcp https://github.com/zereight/gitlab-mcp and brew install zereight/gitlab-mcp/zereight-mcp-gitlab.

Read the token without echo, then export it. The shell history keeps the variable name.

| Client | Install |

| Claude Code | claude mcp add gitlab --transport stdio --scope local --env GITLAB_PERSONAL_ACCESS_TOKEN="$GITLAB_PERSONAL_ACCESS_TOKEN" --env GITLAB_API_URL=https://gitlab.com/api/v4 -- zereight-mcp-gitlab | | Codex | codex mcp add gitlab --env GITLAB_PERSONAL_ACCESS_TOKEN="$GITLAB_PERSONAL_ACCESS_TOKEN" --env GITLAB_API_URL=https://gitlab.com/api/v4 -- zereight-mcp-gitlab | | Cursor | Cursor setup guide | | VS Code | VS Code setup guide | | JSON clients | JSON-based MCP clients setup guide |

@zereight/mcp-gitlab

Agent-workflow-optimized GitLab MCP — manage projects, merge requests, issues, pipelines, wiki, releases, tags, milestones, and more through stdio, SSE, and Streamable HTTP.

Supports PAT, OAuth, read-only mode, dynamic API URLs, and remote authorization for VS Code, Claude, Cursor, Copilot, and other MCP clients.

Why use this GitLab MCP?

• 276 tools: 274 in toolsets + execute_graphql + discover_tools — start with a small toolset; activate more at runtime without CQRS-style grouping • MR 2-step review — list_merge_request_changed_files → batched get_merge_request_file_diff • Agent Skill built in — workflow guidance in skills/gitlab-mcp/ • Flexible auth — Personal Access Token, local OAuth2 browser flow, MCP OAuth proxy, and per-request remote authorization • Multiple transports — stdio for local clients, SSE for legacy clients, and Streamable HTTP for modern remote deployments • Client-friendly setup — examples for Claude Code, Codex, Antigravity, OpenCode, Copilot, Cline, Roo Code, Cursor, Kilo Code, and Amp Code • Self-hosted ready — works with custom GitLab instances, proxy settings, and dynamic API URL routing • JMESPath result filtering — optional jmespath on tool calls (see tools/list) shrinks JSON results without changing GitLab API requests; when response masking is enabled, JMESPath runs on masked data.

How we compare

| | @zereight/mcp-gitlab | GitLab MCP A (community CQRS-style) | GitLab official MCP server |

| Best for | AI agent workflows | Enterprise multi-instance / grouped tools | Built into GitLab, no separate install | | Tool model | 276 tools: 274 in toolsets + execute_graphql + discover_tools | ~50–60 grouped browse_* / manage_* tools | Toolsets chosen with an HTTP header | | MR review | 2-step batched diff | Varies | get_merge_request with diffs | | Node.js | >=18.17 | Often >=24 | Node.js 20+ for stdio via mcp-remote | | License | MIT | Varies | Part of GitLab |

Full comparison with GitLab MCP A →

GitLab also ships an official MCP server.

• Free, Premium, and Ultimate. Moved from Premium to Free in GitLab 19.2. Generally available in GitLab 19.5. • On GitLab.com, a top-level group Owner allows access to the MCP server. On GitLab Self-Managed and GitLab Dedicated, an administrator controls the instance setting. Default rules are on the official page. • Remote clients use HTTP https:///api/v4/mcp with OAuth 2.0 dynamic client registration. • stdio goes through mcp-remote and needs Node.js 20 or later. • Toolsets use the X-Gitlab-Enabled-Mcp-Server-Toolsets header. An optional X-Gitlab-Mcp-Server-Tool-Name-Prefix header keeps the first 32 characters of a tool-name prefix.

Quick start: choose either Personal Access Token or OAuth2 setup below, install @zereight/mcp-gitlab, and use zereight-mcp-gitlab in your MCP client configuration.

Client Setup Guides

• Claude Code Setup Guide • VS Code Setup Guide • GitHub Copilot Setup Guide • Codex Setup Guide • Cursor Setup Guide • JSON-Based MCP Clients Setup Guide - for Factory AI Droid, OpenClaw, and OpenCode style clients • OAuth2 Authentication Setup Guide • Environment Variables Reference • Stateless Mode — Multi-Pod HPA • Custom Agents and Multiple PAT Setup

Usage

Setup Overview

Authentication Methods

The server supports four authentication methods:

For local/desktop use (most common):

1. Personal Access Token (GITLAB_PERSONAL_ACCESS_TOKEN or GITLAB_PERSONAL_ACCESS_TOKEN_FILE) — simplest setup 2. OAuth2 — Local Browser (GITLAB_USE_OAUTH) — recommended for better security

For server/remote deployments:

3. OAuth2 — MCP Proxy (GITLAB_MCP_OAUTH) — for remote MCP clients such as Claude.ai 4. Remote Authorization (REMOTE_AUTHORIZATION) — multi-user deployments where each caller provides their own token

Quick setup paths

• Claude Code: see Claude Code Setup Guide • VS Code: see VS Code Setup Guide • GitHub Copilot: see GitHub Copilot Setup Guide • Codex: see Codex Setup Guide • Cursor: see Cursor Setup Guide • Factory AI Droid / OpenClaw / OpenCode style clients: see JSON-Based MCP Clients Setup Guide • OAuth browser flow details: see OAuth2 Authentication Setup Guide • OAuth without a localhost callback (SSO, remote shell, background clients): run zereight-mcp-gitlab auth (GitLab 17.9+ device flow; 17.2–17.8 need oauth2_device_grant_flow), then start the server with GITLAB_USE_OAUTH=true. See standalone device-flow command.

For the simplest local setup, start with a Personal Access Token. For browser-based local auth, use OAuth2. For remote or multi-user deployments, continue to the MCP OAuth and Remote Authorization sections later in this README.

Install the server once:

Or with npm:

Or with Nix, by adding this flake to your own:

The store path is pinned by your lock file; update it with nix flake update gitlab-mcp.…

Description from the npm listing.