GitLab 19.5, released on October 15, 2026, made the GitLab MCP server generally available and expanded how external AI agents can interact with its DevSecOps platform. This is a retrospective report based on an article published November 15, 2026.
Through the Model Context Protocol (MCP), compatible tools such as Claude Code and Cursor can access a broader set of GitLab tools and invoke GitLab Duo Agent Platform agents and workflows. New tools support group discovery, inspection of individual CI/CD artifact files, and launching or monitoring Duo agents and workflows. Administrators can choose which MCP toolsets to expose, limiting unnecessary tools and their use of model context.
On GitLab.com, MCP requests are limited to 60 per minute for Free users and 600 per minute for Premium and Ultimate users. Reconnection and retry requests count toward those limits.
The release also extends AI governance beyond GitLab’s own agents. Organizations can connect tools including Claude Code, Cursor and Codex through the GitLab CLI. Once configured, GitLab can record eligible agent sessions with the user, agent, project and time, display that activity alongside GitLab agent activity, and stream audit events to a SIEM system.
GitLab Duo CLI gained an automatic mode that lets agents run tools without requesting approval for every shell command, Git operation or MCP call. It is off by default and can be controlled at the instance, group and project levels; tools marked “Always Deny” remain blocked. The /goal command also became generally available, allowing developers to describe an open-ended objective for Duo to handle through a governed implementation and verification process.
Separately, GitLab Secrets Manager became generally available. Built on OpenBao, it integrates with GitLab group and project permissions, scopes secrets to the tasks that need them, and generates audit events for secret operations. Expanded security configuration templates let organizations centrally set options for Secret Detection and SAST, including excluded paths, analyzer images and full-history scans, rather than repeating them in each project’s CI/CD configuration.
Source: infoq.cn (originally published 2026-11-15 09:00 UTC+8)