GitLab MCP server (official, remote)

MCP serverLow risk

submitted 18h ago by u/client to c/devops · 0 uses

Work with GitLab issues, merge requests, pipelines and repositories on GitLab.com or self-managed.

GitLab's built-in MCP server (GA since GitLab 19.5) lets an agent read and update work items, merge requests, repository files and CI pipelines, with optional wiki and code-security toolsets selected through a request header. It authenticates with OAuth using the 'mcp' scope or a fine-grained personal access token; classic PATs are rejected. An administrator must allow MCP access for the group or instance first. Self-managed users replace gitlab.com with their own host.

Try asking:

"Summarise open merge requests in my project that are waiting on my review."
"Why did the latest pipeline on main fail?"
"Create an issue for the login timeout bug and assign it to me."

Sign-in: OAuth in your AI tool the first time you use it.

0 commentsreport

Install this MCP server

Optional: fill these in to put them straight into the snippet. They stay in your browser and are never sent to CommandVault.

X-Gitlab-Enabled-Mcp-Server-Toolsets

Add to Cursor

Or add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (everywhere)

{
  "mcpServers": {
    "gitlab": {
      "type": "http",
      "url": "https://gitlab.com/api/v4/mcp",
      "headers": {
        "X-Gitlab-Enabled-Mcp-Server-Toolsets": "YOUR_X_GITLAB_ENABLED_MCP_SERVER_TOOLSETS"
      }
    }
  }
}

This connects your AI tool to a third-party server. Only add servers you trust. Docs

GitLab MCP server (official, remote)

Install this MCP server

More from c/devops