GitLab MCP Server

by zereight·io.github.zereight/gitlab-mcp·v2.3.19·2.0k stars

No reviews yet

GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.

B83/100grade B

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

B83/100

not scanned yet

Adoption

Widely used

2.0k stars140k downloads/wk

Reviews

Write one

Nobody has reviewed GitLab MCP Server yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

GitLab MCP Server tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How GitLab MCP Server compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 83/100; higher than 65% of 1,119 Developer tools servers
GitHub stars: 2,044; more than 95% of 855 Developer tools servers
Downloads a week: 140,283; more than 97% of 436 Developer tools servers with a package

Release history: 24 versions in the registry since 2026-09-16, latest 2026-11-01, typically one every 1 day.

Install GitLab MCP Server in Claude Code, Cursor or VS Code

Runs npx -y @zereight/mcp-gitlab on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add gitlab-mcp -- npx -y @zereight/mcp-gitlab

Add to Cursor

What the publisher says

From the GitLab MCP Server repository's README, as published. We do not edit it. Read it on GitHub

GitLab MCP Server

English | 한국어 | 简体中文

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

@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?

261 tools + discovertools** — start with a small toolset; activate more at runtime without CQRS-style grouping
MR 2-step review — listmergerequestchangedfiles → batched getmergerequestfilediff
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

How we compare

Full comparison →

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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

GitLab MCP Server: common questions

Is GitLab MCP Server safe?: Mostly: it is graded B (83/100). Read the GitLab MCP Server safety report
How do I install GitLab MCP Server?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does GitLab MCP Server need an API key?: Yes. The registry entry asks for GITLAB_PERSONAL_ACCESS_TOKEN, GITLAB_JOB_TOKEN.
Is GitLab MCP Server maintained?: The last commit was 20 days ago (2026-10-15). The latest release is v2.3.19.
What can I use instead of GitLab MCP Server?: Servers from other publishers that do the same job: Gk CLI MCP server, Sentry MCP server and GitHub MCP server.
How does GitLab MCP Server compare with other Developer tools MCP servers?: safety score 83/100 (higher than 65% of 1,119 Developer tools servers); github stars 2,044 (more than 95% of 855 Developer tools servers); downloads a week 140,283 (more than 97% of 436 Developer tools servers with a package). Full comparison.

Alternatives to GitLab MCP Server

Same job from other publishers: the closest match first, then the best rated.

Gk CLI
The GitKraken MCP Server for managing repos, PRs, issues across GitHub, GitLab, Bitbucket and more.
not reviewed
Established
B
Sentry
MCP server for Sentry - error monitoring, issue tracking, and debugging for AI assistants
not reviewed
Widely used
A
GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
not reviewed
Established
A
walkerOS Flow
Build, validate, simulate, and deploy walkerOS event pipelines
not reviewed
Established
B
Atlassian Dc Jira
MCP server for Atlassian Jira Data Center - search, view, and create issues
not reviewed
Established
B

GitLab MCP Server vs Gk CLI

Run it through the gateway

Local package. It runs on your machine, not through the gateway.

Rating: —
Safety grade: B · 83/100
Stars: 2.0k
Downloads/wk: 140k
Price: Free
Licence: MIT
Transport: Local · mixed
Version: 2.3.19
Category: Developer tools
Last release: 2026-10-15

Credentials it needs

GITLAB_PERSONAL_ACCESS_TOKENsecretGitLab personal access token for local stdio use. A non-empty value overrides GITLAB_PERSONAL_ACCESS_TOKEN_FILE. One of this token, GITLAB_PERSONAL_ACCESS_TOKEN_FILE, GITLAB_JOB_TOKEN, GITLAB_AUTH_COOKIE_PATH, or GITLAB_USE_OAUTH=true must be set. Create a token with the GitLab scopes the tools need, such as api or read_api.
GITLAB_PERSONAL_ACCESS_TOKEN_FILEPath to a file that contains the personal access token. Read once at startup and trimmed. Ignored when GITLAB_PERSONAL_ACCESS_TOKEN or --token is non-empty. A missing, unreadable, or empty file stops startup. Does not replace job token, OAuth, cookie, or remote authorization.
GITLAB_JOB_TOKENsecretOptional GitLab CI job token to use instead of a personal access token when running inside GitLab CI.
GITLAB_AUTH_COOKIE_PATHOptional path to a GitLab authentication cookie file for cookie-based authentication.
GITLAB_USE_OAUTHSet to true to start with GitLab OAuth instead of a personal access token, job token, or cookie file.
GITLAB_OAUTH_CLIENT_IDGitLab OAuth application ID. When GITLAB_USE_OAUTH=true, set this or GITLAB_OAUTH_TOKEN_SCRIPT.
GITLAB_OAUTH_TOKEN_SCRIPTCommand that prints an OAuth access token. When GITLAB_USE_OAUTH=true, set this or GITLAB_OAUTH_CLIENT_ID.
GITLAB_API_URLGitLab API base URL. Use https://gitlab.com/api/v4 for GitLab.com or your self-managed GitLab API URL.
GITLAB_ALLOWED_PROJECT_IDSOptional comma-separated list of GitLab project IDs that this server is allowed to access.
GITLAB_PERMISSION_MODETool exposure. Allowed values are readonly, modify, and full. Unset uses full. readonly keeps read-only tools. modify blocks delete and teardown tools.
GITLAB_TOOLSETSOptional comma-separated list of toolsets to enable, such as projects, issues, merge_requests, pipelines, releases, users, groups, wiki, or search.
GITLAB_TOOLSOptional comma-separated list of individual tool names to add on top of enabled toolsets.
GITLAB_DENIED_TOOLS_REGEXOptional regular expression used to hide matching tools from the server.
GITLAB_TOOL_POLICY_APPROVEOptional comma-separated list of tool names that require explicit approval before execution.
GITLAB_TOOL_POLICY_HIDDENOptional comma-separated list of tool names to hide from tools/list.
NODE_TLS_REJECT_UNAUTHORIZEDSet to 0 only when you intentionally need to connect to a GitLab instance with invalid or self-signed TLS certificates.
GITLAB_CA_CERT_PATHOptional path to a custom CA certificate file for self-managed GitLab instances.
GITLAB_MASKING_ENABLEDSet to true to mask text tool results and returned errors using built-in or configured rules.
GITLAB_MASKING_CONFIGOptional path to a response-masking JSON configuration file.
GITLAB_MASKING_POLICY_FILEOptional protected server-owned JSON file containing managed masking policies.
GITLAB_MASKING_WORKSPACE_DIRDirectory used to resolve response-masking configuration paths.
GITLAB_PERSONAL_ACCESS_TOKENsecretGitLab personal access token for local stdio use. A non-empty value overrides GITLAB_PERSONAL_ACCESS_TOKEN_FILE. One of this token, GITLAB_PERSONAL_ACCESS_TOKEN_FILE, GITLAB_JOB_TOKEN, GITLAB_AUTH_COOKIE_PATH, or GITLAB_USE_OAUTH=true must be set. Create a token with the GitLab scopes the tools need, such as api or read_api.
GITLAB_PERSONAL_ACCESS_TOKEN_FILEPath to a file that contains the personal access token. Read once at startup and trimmed. Ignored when GITLAB_PERSONAL_ACCESS_TOKEN or --token is non-empty. A missing, unreadable, or empty file stops startup. Does not replace job token, OAuth, cookie, or remote authorization.
GITLAB_JOB_TOKENsecretOptional GitLab CI job token to use instead of a personal access token when running inside GitLab CI.
GITLAB_AUTH_COOKIE_PATHOptional path to a GitLab authentication cookie file for cookie-based authentication.
GITLAB_USE_OAUTHSet to true to start with GitLab OAuth instead of a personal access token, job token, or cookie file.
GITLAB_OAUTH_CLIENT_IDGitLab OAuth application ID. When GITLAB_USE_OAUTH=true, set this or GITLAB_OAUTH_TOKEN_SCRIPT.
GITLAB_OAUTH_TOKEN_SCRIPTCommand that prints an OAuth access token. When GITLAB_USE_OAUTH=true, set this or GITLAB_OAUTH_CLIENT_ID.
GITLAB_API_URLGitLab API base URL. Use https://gitlab.com/api/v4 for GitLab.com or your self-managed GitLab API URL.
GITLAB_ALLOWED_PROJECT_IDSOptional comma-separated list of GitLab project IDs that this server is allowed to access.
GITLAB_PERMISSION_MODETool exposure. Allowed values are readonly, modify, and full. Unset uses full. readonly keeps read-only tools. modify blocks delete and teardown tools.
GITLAB_TOOLSETSOptional comma-separated list of toolsets to enable, such as projects, issues, merge_requests, pipelines, releases, users, groups, wiki, or search.
GITLAB_TOOLSOptional comma-separated list of individual tool names to add on top of enabled toolsets.
GITLAB_DENIED_TOOLS_REGEXOptional regular expression used to hide matching tools from the server.
GITLAB_TOOL_POLICY_APPROVEOptional comma-separated list of tool names that require explicit approval before execution.
GITLAB_TOOL_POLICY_HIDDENOptional comma-separated list of tool names to hide from tools/list.
NODE_TLS_REJECT_UNAUTHORIZEDSet to 0 only when you intentionally need to connect to a GitLab instance with invalid or self-signed TLS certificates.
GITLAB_CA_CERT_PATHOptional path to a custom CA certificate file for self-managed GitLab instances.
GITLAB_MASKING_ENABLEDSet to true to mask text tool results and returned errors using built-in or configured rules.
GITLAB_MASKING_CONFIGOptional path to a response-masking JSON configuration file.
GITLAB_MASKING_POLICY_FILEOptional protected server-owned JSON file containing managed masking policies.
GITLAB_MASKING_WORKSPACE_DIRDirectory used to resolve response-masking configuration paths.

Own this server?

Claim it to keep the listing current and reply to reviews. Claiming never changes the grade or hides a review.

Claim listing

Badge for your README

Shows the safety grade and links back to this page. It updates itself after every scan and review.

[![mcp.market](https://mcp.market/badge/zereight-gitlab-mcp.svg)](https://mcp.market/server/zereight-gitlab-mcp)

How the badge works