GitLab (community)

§1What it does

A widely used community-maintained MCP server for GitLab. It exposes tools for merge requests, diffs, pipelines and jobs, groups, environments and generic GitLab API requests. The original reference GitLab server from the MCP project is archived. Since v2.3.6 every GITLAB_API_URL entry must start with http:// or https://, and a comma in an embedded password must be written as %2C.

§2Setup

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

Snippets adapted from the official documentation. Check the official page for current options and auth requirements.

§2bWhen you disconnect

1. Removed locallyClear the sign-in or remove the server in your MCP client (for example claude mcp logout or claude mcp remove in Claude Code, or log out of the server in Cursor). This only deletes the client's copy of the tokens.
2. Authorization revokedFind zereight (community)'s connected-apps / authorized applications page and revoke the grant there. We haven't found an official page for it yet. This is what stops the refresh token; clearing the client alone is not enough.

Why both steps: OAuth token refresh in the security checklist.

§3Prompts to try

1. “Review the diff of merge request !42 and list risky changes.”Copy
2. “Why did the latest pipeline on main fail?”Copy
3. “Validate this .gitlab-ci.yml before I push it.”Copy