Developer · Local MCP server
Gitlab MCP
GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.zereight/gitlab-mcp- Version
- 2.1.69
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- zereight (GitHub)
- Repository
- github.com/zereight/gitlab-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @zereight/mcp-gitlab | 2.1.69 | stdio |
How to connect Gitlab MCP
Gitlab MCP runs locally from a Node.js package published to the npm registry: @zereight/mcp-gitlab version 2.1.69. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @zereight/mcp-gitlab@2.1.69. It reads these environment variables: GITLAB_PERSONAL_ACCESS_TOKEN (required, secret), GITLAB_JOB_TOKEN (secret), GITLAB_AUTH_COOKIE_PATH, GITLAB_API_URL, GITLAB_ALLOWED_PROJECT_IDS, GITLAB_READ_ONLY_MODE, USE_GITLAB_WIKI, GITLAB_TOOLSETS, GITLAB_TOOLS, GITLAB_DENIED_TOOLS_REGEX, GITLAB_TOOL_POLICY_APPROVE, GITLAB_TOOL_POLICY_HIDDEN, NODE_TLS_REJECT_UNAUTHORIZED, GITLAB_CA_CERT_PATH, GITLAB_MASKING_ENABLED, GITLAB_MASKING_CONFIG, GITLAB_MASKING_POLICY_FILE and GITLAB_MASKING_WORKSPACE_DIR; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"gitlab-mcp": {
"command": "npx",
"args": [
"-y",
"@zereight/mcp-gitlab@2.1.69"
],
"env": {
"GITLAB_PERSONAL_ACCESS_TOKEN": "<secret>",
"GITLAB_JOB_TOKEN": "<secret>",
"GITLAB_AUTH_COOKIE_PATH": "<value>",
"GITLAB_API_URL": "<value>",
"GITLAB_ALLOWED_PROJECT_IDS": "<value>",
"GITLAB_READ_ONLY_MODE": "<value>",
"USE_GITLAB_WIKI": "<value>",
"GITLAB_TOOLSETS": "<value>",
"GITLAB_TOOLS": "<value>",
"GITLAB_DENIED_TOOLS_REGEX": "<value>",
"GITLAB_TOOL_POLICY_APPROVE": "<value>",
"GITLAB_TOOL_POLICY_HIDDEN": "<value>",
"NODE_TLS_REJECT_UNAUTHORIZED": "<value>",
"GITLAB_CA_CERT_PATH": "<value>",
"GITLAB_MASKING_ENABLED": "<value>",
"GITLAB_MASKING_CONFIG": "<value>",
"GITLAB_MASKING_POLICY_FILE": "<value>",
"GITLAB_MASKING_WORKSPACE_DIR": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Gitlab Ci MCPGitLab CI/CD MCP — pipelines, jobs, schedules, MRs, files. Any GitLab (SaaS or self-hosted). | Local · stdio |
| GitLab Documentation MCP ServerSearchable access to GitLab documentation from multiple repositories with full-text search. | Local · stdio |
| Gitlab MCPGitLab over MCP from your own account: issues, merge requests, reviews, the repository and CI. | Local · stdio |
| Gitlab MCPPublic GitLab projects and users. No key required. | Local · stdio |
| GitLab MCP ServerGo MCP server for GitLab: 2 dynamic tools reach 1000+ REST/GraphQL actions. Free/CE, no paid tier. | Remote & Local · HTTP, stdio |
| Gitlab PublicGitLab Public MCP — wraps the GitLab REST API v4 (public endpoints, no auth) | Remote · HTTP |
| GitmemPersistent institutional memory for AI coding agents. Memory that compounds. | Local · stdio |
| GitPinProve and verify multi-repo claims at Git HEAD: path, line, full SHA, no index. | Local · stdio |