GitLab MCP Server

com.gitlab/mcp

Documentation

Installation

Connect to the hosted GitLab MCP endpoint at https://gitlab.com/api/v4/mcp with an MCP client over HTTP. GitLab also documents stdio access through mcp-remote for clients that need a proxy.

Configuration

GitLab documents HTTP transport setup for Cursor, Claude Code, Claude Desktop, Gemini Code Assist and Gemini CLI, GitHub Copilot in VS Code, Kiro IDE and CLI, OpenAI Codex, and Zed. The server supports OAuth 2.0 Dynamic Client Registration, and HTTP tool-name prefixing can be enabled with the X-Gitlab-Mcp-Server-Tool-Name-Prefix header.

Prerequisites

GitLab Duo availability must be enabled, beta and experimental features must be on, and access to the MCP server must be allowed. Node.js 20 or later is required for stdio-based clients and related troubleshooting flows.

Capabilities

GitLab MCP tools expose project information, issue data, merge request data, pipeline data, and related GitLab operations.

Limitations

GitLab warns to guard against prompt injection and to use MCP tools only on GitLab objects you trust. OAuth DCR creates client applications per MCP client unless you reuse a shared OAuth application with a matching redirect URI.