GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
Indexed, not yet reviewed
We found GitLab MCP Server in the official MCP registry. Our automated check passed on Nov 1, 2026 (it confirms the server is published and reachable), but no one at CuratedMCP has reviewed its code, permissions or credentials handling. Check what it can access before you give it keys. Scan your machine free to see every MCP server you have installed.
{
"mcpServers": {
"gitlab": {
"command": "npx",
"args": [
"-y",
"@zereight/mcp-gitlab"
]
}
}
}| Environment variable | Required | What it is |
|---|---|---|
| GITLAB_PERSONAL_ACCESS_TOKENsecret | No | GitLab 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_COO |
| GITLAB_PERSONAL_ACCESS_TOKEN_FILE | No | Path 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 |
| GITLAB_JOB_TOKENsecret | No | Optional GitLab CI job token to use instead of a personal access token when running inside GitLab CI. |
| GITLAB_AUTH_COOKIE_PATH | No | Optional path to a GitLab authentication cookie file for cookie-based authentication. |
| GITLAB_USE_OAUTH | No | Set to true to start with GitLab OAuth instead of a personal access token, job token, or cookie file. |
| GITLAB_OAUTH_CLIENT_ID | No | GitLab OAuth application ID. When GITLAB_USE_OAUTH=true, set this or GITLAB_OAUTH_TOKEN_SCRIPT. |
| GITLAB_OAUTH_TOKEN_SCRIPT | No | Command that prints an OAuth access token. When GITLAB_USE_OAUTH=true, set this or GITLAB_OAUTH_CLIENT_ID. |
| GITLAB_API_URL | No | GitLab API base URL. Use https://gitlab.com/api/v4 for GitLab.com or your self-managed GitLab API URL. |
| GITLAB_ALLOWED_PROJECT_IDS | No | Optional comma-separated list of GitLab project IDs that this server is allowed to access. |
| GITLAB_PERMISSION_MODE | No | Tool exposure. Allowed values are readonly, modify, and full. Unset uses full. readonly keeps read-only tools. modify blocks delete and teardown tools. |
| GITLAB_TOOLSETS | No | Optional comma-separated list of toolsets to enable, such as projects, issues, merge_requests, pipelines, releases, users, groups, wiki, or search. |
| GITLAB_TOOLS | No | Optional comma-separated list of individual tool names to add on top of enabled toolsets. |
| GITLAB_DENIED_TOOLS_REGEX | No | Optional regular expression used to hide matching tools from the server. |
| GITLAB_TOOL_POLICY_APPROVE | No | Optional comma-separated list of tool names that require explicit approval before execution. |
| GITLAB_TOOL_POLICY_HIDDEN | No | Optional comma-separated list of tool names to hide from tools/list. |
| NODE_TLS_REJECT_UNAUTHORIZED | No | Set to 0 only when you intentionally need to connect to a GitLab instance with invalid or self-signed TLS certificates. |
| GITLAB_CA_CERT_PATH | No | Optional path to a custom CA certificate file for self-managed GitLab instances. |
| GITLAB_MASKING_ENABLED | No | Set to true to mask text tool results and returned errors using built-in or configured rules. |
| GITLAB_MASKING_CONFIG | No | Optional path to a response-masking JSON configuration file. |
| GITLAB_MASKING_POLICY_FILE | No | Optional protected server-owned JSON file containing managed masking policies. |
| GITLAB_MASKING_WORKSPACE_DIR | No | Directory used to resolve response-masking configuration paths. |
Claim this page to get a full CuratedMCP listing: edit your description, see listing analytics, and add our README badge. Listing is free, and a person checks every submission before it goes live. We'll pre-fill the form from the registry.