GitLab MCP Server (zereight)

Add to your client

Copy the config for your MCP client and paste it into its config file.

{
  "mcpServers": {
    "gitlab-mcp-server-zereight": {
      "command": "npx",
      "args": [
        "-y",
        "@zereight/mcp-gitlab"
      ],
      "env": {
        "GITLAB_API_URL": "https://gitlab.com/api/v4",
        "GITLAB_PERSONAL_ACCESS_TOKEN": "<your-gitlab-token>"
      }
    }
  }
}

Before you start

• Node.js 18 or later (or Docker to run the zereight050/gitlab-mcp image)
• A GitLab Personal Access Token with at least the `api` scope (create it under GitLab > User Settings > Access Tokens)
• Your GitLab API URL, e.g. https://gitlab.com/api/v4 for SaaS or your self-hosted instance URL
• An MCP-capable client (Claude Desktop, Cursor, VS Code, etc.)

About GitLab MCP Server (zereight)

Tools & capabilities (12)

When to use it

• Use it when you want an assistant to open, review, comment on, or merge GitLab merge requests directly from your editor
• Use it when triaging or bulk-creating issues across one or more GitLab projects
• Use it when debugging CI failures and you need pipeline status and job log output without leaving your chat
• Use it when you maintain a self-hosted GitLab instance and need a token-based, read-only-capable MCP integration
• Use it when you want the assistant to read and edit repository files, wikis, or releases as part of a coding task

Quick setup

1. 1Create a GitLab Personal Access Token with the `api` scope
2. 2Add the server to your MCP client config, running `npx @zereight/mcp-gitlab` (or the Docker image)
3. 3Set the `GITLAB_PERSONAL_ACCESS_TOKEN` and `GITLAB_API_URL` environment variables
4. 4Optionally set `GITLAB_READ_ONLY_MODE=true` to restrict to read-only tools
5. 5Restart your MCP client and confirm the GitLab tools are listed
6. 6Verify by asking the assistant to list issues or merge requests for a known project

GitLab MCP Server (zereight) FAQ