gitlab-mcp

Package (npm 2.1.66)

npx -y @zereight/mcp-gitlab@2.1.66

Or add to your MCP client config:

{
  "mcpServers": {
    "gitlab-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@zereight/mcp-gitlab@2.1.66"
      ],
      "env": {
        "GITLAB_PERSONAL_ACCESS_TOKEN": "<YOUR_VALUE>",
        "GITLAB_JOB_TOKEN": "<YOUR_VALUE>",
        "GITLAB_AUTH_COOKIE_PATH": "<YOUR_VALUE>",
        "GITLAB_API_URL": "<YOUR_VALUE>",
        "GITLAB_ALLOWED_PROJECT_IDS": "<YOUR_VALUE>",
        "GITLAB_READ_ONLY_MODE": "<YOUR_VALUE>",
        "USE_GITLAB_WIKI": "<YOUR_VALUE>",
        "GITLAB_TOOLSETS": "<YOUR_VALUE>",
        "GITLAB_TOOLS": "<YOUR_VALUE>",
        "GITLAB_DENIED_TOOLS_REGEX": "<YOUR_VALUE>",
        "GITLAB_TOOL_POLICY_APPROVE": "<YOUR_VALUE>",
        "GITLAB_TOOL_POLICY_HIDDEN": "<YOUR_VALUE>",
        "NODE_TLS_REJECT_UNAUTHORIZED": "<YOUR_VALUE>",
        "GITLAB_CA_CERT_PATH": "<YOUR_VALUE>",
        "GITLAB_MASKING_ENABLED": "<YOUR_VALUE>",
        "GITLAB_MASKING_CONFIG": "<YOUR_VALUE>",
        "GITLAB_MASKING_POLICY_FILE": "<YOUR_VALUE>",
        "GITLAB_MASKING_WORKSPACE_DIR": "<YOUR_VALUE>"
      }
    }
  }
}

• GITLAB_PERSONAL_ACCESS_TOKEN required secret — 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 secret — Optional GitLab CI job token to use instead of a personal access token when running inside GitLab CI.
• GITLAB_AUTH_COOKIE_PATH — Optional path to a GitLab authentication cookie file for cookie-based authentication.
• GITLAB_API_URL — GitLab API base URL. Use https://gitlab.com/api/v4 for GitLab.com or your self-managed GitLab API URL.
• GITLAB_ALLOWED_PROJECT_IDS — Optional comma-separated list of GitLab project IDs that this server is allowed to access.
• GITLAB_READ_ONLY_MODE — Set to true to expose only read-only tools and block write operations.
• USE_GITLAB_WIKI — Set to true to enable GitLab wiki tools.
• GITLAB_TOOLSETS — Optional comma-separated list of toolsets to enable, such as projects, issues, merge_requests, pipelines, releases, users, groups, wiki, or search.
• GITLAB_TOOLS — Optional comma-separated list of individual tool names to add on top of enabled toolsets.
• GITLAB_DENIED_TOOLS_REGEX — Optional regular expression used to hide matching tools from the server.
• GITLAB_TOOL_POLICY_APPROVE — Optional comma-separated list of tool names that require explicit approval before execution.
• GITLAB_TOOL_POLICY_HIDDEN — Optional comma-separated list of tool names to hide from tools/list.
• NODE_TLS_REJECT_UNAUTHORIZED — 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 — Optional path to a custom CA certificate file for self-managed GitLab instances.
• GITLAB_MASKING_ENABLED — Set to true to mask text tool results and returned errors using built-in or configured rules.
• GITLAB_MASKING_CONFIG — Optional path to a response-masking JSON configuration file.
• GITLAB_MASKING_POLICY_FILE — Optional protected server-owned JSON file containing managed masking policies.
• GITLAB_MASKING_WORKSPACE_DIR — Directory used to resolve response-masking configuration paths.