Gitlab MCP Server

What the code does

We read the source, 17 h ago · rules 3dff92dd89df

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

  paths.push(process.env.NPM_CONFIG_USERCONFIG ?? join(homedir(), ".npmrc"));

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

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

{
  "mcpServers": {
    "gitlab-mcp": {
      "args": [
        "-y",
        "@zereight/mcp-gitlab"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.gitlab-mcp]
command = "npx"
args = ["-y", "@zereight/mcp-gitlab"]

{
  "mcpServers": {
    "gitlab-mcp": {
      "args": [
        "-y",
        "@zereight/mcp-gitlab"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "gitlab-mcp": {
      "args": [
        "-y",
        "@zereight/mcp-gitlab"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: GITLAB_PERSONAL_ACCESS_TOKEN (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 (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.). The author declared them in the registry entry; get the values from the project itself.