Trending:
OpenAI admin controls GitHub Issues agent approvals Gemini in Chrome UK expansion Developer tools coverage
TECHSTAGED Better software. Smarter business.

GitLab MCP server GA: Connecting external agents to your software lifecycle

By TechStaged

· 2 min read

Prepared with AI assistance from source material. Automated editorial review recorded . Automated checks can miss errors and do not represent human approval. Editorial policy and corrections.

Diagram showing GitLab MCP server connecting external agents to the software lifecycle
TechStaged-owned

Summary

  • The MCP server is now generally available.
  • The MCP server connects external agents to the entire software lifecycle—from planning through production.
  • On GitLab.com, per-user rate limits are 60 calls per minute on Free and 600 on Premium and Ultimate.
  • In 19.5, the MCP server’s tool catalog is simpler to work with and toolsets are available to tailor which groups of tools are returned.

The GitLab MCP server has reached general availability, signaling broader participation of external agents in GitLab workflows. The announcement frames MCP as a bridge between agents and GitLab’s software lifecycle, enabling agents to operate across planning, code, and production with fewer calls and leaner context.

WHAT IT CONNECTS TO ACROSS THE LIFECYCLE

The MCP server connects your team’s external agents to your entire software lifecycle—from planning through production. This enables agents to run GitLab workflows from the client your team already uses, with interactions happening in fewer calls and with less context to carry through each task.

REDUCING CONTEXT AND API CALLS

A key claim is that agents using APIs for disparate tools often guess endpoints and exhaust context windows. The MCP server is designed to provide a curated set of tools and a more focused context per task, reducing unnecessary data movement and calls.

TOOL CATALOG, TOOLSETS, AND PERMISSIONS

In version 19.5, the MCP server includes a simplified tool catalog, with toolsets that let teams choose focused groups of tools. Tools such as get_merge_request, get_pipeline, and related capabilities are described to help agents find the information they need without extra steps. Actions still run within the permissions you’ve configured in GitLab.

INTEGRATION WITH DUO AGENT PLATFORM

Agents can hand work to GitLab Duo Agent Platform and follow that job to the result without leaving the client. The workflow runs in a CI job inside GitLab, under the same context layer, policy checks, and audit trail as any other Duo Agent Platform session. When a decision is needed, the session pauses for human input and then resumes.

GETTING STARTED AND AVAILABILITY

The MCP server is available on GitLab.com, GitLab Self-Managed, and GitLab Dedicated, including Free, Premium, and Ultimate tiers. A free trial for Duo Agent Platform is available, and GitLab Credits are included with Premium or Ultimate subscriptions. Per-user rate limits on GitLab.com are 60 calls per minute on Free and 600 on Premium and Ultimate.

SOURCES

Developer Tools GitLab arms developers with cost controls for AI agents via Duo Agent Platform and Orbit • 3 min read Developer Tools Gemini 4 Argon arrives on GitLab Duo Agent Platform to power long-horizon engineering work • 3 min read Developer Tools GitLab Credits Bring Usage-Based Pricing to Duo Agent Platform • 2 min read Developer Tools GPT-6 Astra on GitLab Duo Agent Platform delivers faster runs and fewer tokens • 2 min read Developer Tools GitLab's AI Governance Dashboard beta: a single view of agent activity • 2 min read Developer Tools GitLab’s Business Logic Security Analyzer: what verified evidence reveals beyond the announcement • 2 min read Security Agents are your newest insiders: Security must move at their speed • 2 min read Developer Tools Thin Orchestrator, Deep Specialists: How Meta’s 1,300-Line Router Strategy Aims to Make AI Agents More Reliable • 3 min read