gitlab-mcp

What it does

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

Description as published by the publisher in the official MCP Registry, read 10 Oct 2026. Not written or verified by Few Servers.

Facts

Install

• npm package, as published: @zereight/mcp-gitlab · version 2.2.2 · transport stdio

  npx -y @zereight/mcp-gitlab

  Standard run command for npm packages. The registry publishes the package name, not a command; check the repository for required arguments.

Install details read from the registry record on 12 Oct 2026. We have not run this server.

Keys and settings

Needs a key or token: the registry record marks a secret value as required. Declared by the publisher:

• GITLAB_PERSONAL_ACCESS_TOKEN (environment variable, secret, required): GitLab personal access token for local stdio use. Create a token with the GitLab scopes needed by the tools you plan to use, such as api or read_api.
• GITLAB_JOB_TOKEN (environment variable, secret, not marked required): Optional GitLab CI job token to use instead of a personal access token when running inside GitLab CI.
• GITLAB_AUTH_COOKIE_PATH (environment variable, not marked required): Optional path to a GitLab authentication cookie file for cookie-based authentication.
• GITLAB_API_URL (environment variable, not marked required): GitLab API base URL. Use https://gitlab.com/api/v4 for GitLab.com or your self-managed GitLab API URL.
• GITLAB_ALLOWED_PROJECT_IDS (environment variable, not marked required): Optional comma-separated list of GitLab project IDs that this server is allowed to access.
• GITLAB_READ_ONLY_MODE (environment variable, not marked required): Deprecated (removed in next major (v3.0.0)); use GITLAB_PERMISSION_MODE=readonly instead.
• USE_GITLAB_WIKI (environment variable, not marked required): Deprecated (removed in next major (v3.0.0)); use GITLAB_TOOLSETS=core,wiki instead. If you already set GITLAB_TOOLSETS, append wiki to your existing list instea
• GITLAB_TOOLSETS (environment variable, not marked required): Optional comma-separated list of toolsets to enable, such as projects, issues, merge_requests, pipelines, releases, users, groups, wiki, or search.
• GITLAB_TOOLS (environment variable, not marked required): Optional comma-separated list of individual tool names to add on top of enabled toolsets.
• GITLAB_DENIED_TOOLS_REGEX (environment variable, not marked required): Optional regular expression used to hide matching tools from the server.
• GITLAB_TOOL_POLICY_APPROVE (environment variable, not marked required): Optional comma-separated list of tool names that require explicit approval before execution.
• GITLAB_TOOL_POLICY_HIDDEN (environment variable, not marked required): Optional comma-separated list of tool names to hide from tools/list.
• NODE_TLS_REJECT_UNAUTHORIZED (environment variable, not marked required): 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 (environment variable, not marked required): Optional path to a custom CA certificate file for self-managed GitLab instances.
• GITLAB_MASKING_ENABLED (environment variable, not marked required): Set to true to mask text tool results and returned errors using built-in or configured rules.
• GITLAB_MASKING_CONFIG (environment variable, not marked required): Optional path to a response-masking JSON configuration file.
• GITLAB_MASKING_POLICY_FILE (environment variable, not marked required): Optional protected server-owned JSON file containing managed masking policies.
• GITLAB_MASKING_WORKSPACE_DIR (environment variable, not marked required): Directory used to resolve response-masking configuration paths.

Links

RepositoryRegistry record (JSON)npm package

Being listed is not a safety check. Read the repository and check what a server asks for before you connect it. How the directory works.