GitLab's MCP server is generally available in 19.5
GitLab 19.5, released October 15, 2026, makes the GitLab MCP server generally available.
·1 min read·AB
GitLab 19.5, released October 15, 2026, makes the GitLab MCP server generally available. An agent that already speaks the Model Context Protocol can work against GitLab from the client a team already uses, instead of guessing REST endpoints and filling its context window with extra calls.
The 19.5 tool list is smaller on purpose. get_merge_request can return commits, diffs, pipelines, conflicts, or notes. get_pipeline now includes the jobs that used to need a separate call. The setup notes name Claude Code, Claude Desktop, Cursor, GitHub Copilot, OpenAI Codex, Gemini, Kiro, Zed, and other MCP clients. The server is on the Free, Premium, and Ultimate tiers, for GitLab.com, self-managed installs, and GitLab Dedicated. On GitLab.com the per-user limit is 60 calls a minute on Free and 600 on Premium and Ultimate. Reconnects and retries count toward that limit, so a chatty agent can hit HTTP 429 before the team has done much real work.
Why it matters
Agents can now sit on a supported GitLab interface instead of a pile of one-off API scripts.
Source: GitLab