Provides tools for monitoring and analyzing GitLab CI/CD pipelines, allowing agents to list pipelines, retrieve job details and logs, and perform failure analysis to identify root causes in error logs.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@GitLab CI MCP ServerAnalyze why the latest pipeline failed and find the root cause"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
GitLab CI MCP Server
Model Context Protocol (MCP) server for GitLab CI/CD pipeline monitoring.
Purpose
Provides AI agents with structured access to GitLab CI/CD pipelines for the egirl-platform project. Enables agents to:
List recent pipelines
Get pipeline details and job information
Retrieve job logs for debugging
Analyze recent failures
Extract likely root causes from error logs
Features
Available Tools
Tool | Description |
| List recent pipelines with status |
| Get detailed info for a specific pipeline |
| List all jobs in a pipeline |
| Retrieve logs for a specific job |
| Get recent failed pipelines with details |
| Analyze failed pipeline and extract error patterns |
Intelligent Features
Error Pattern Extraction: Automatically identifies error lines in logs
Structured Responses: Returns JSON for easy agent parsing
Failure Analysis: Groups related failures and extracts root causes
Auto : Automatically loads
GITLAB_PATfrom project.envfile
Installation
Configuration
The server automatically loads .env from the project root, so no manual configuration needed if you have GITLAB_PAT in your .env file.
For Claude Code MCP Configuration
Add to your Claude Code MCP configuration:
Note: No env section needed - the server loads .env automatically!
Usage
For AI Agents
Agents can invoke MCP tools directly:
Response Format
All tools return structured JSON:
Pipeline List:
Failure Analysis:
Environment Variables
Variable | Description | Required |
| GitLab Personal Access Token | Yes |
The server checks for both GITLAB_PAT (preferred) and GPLAT (legacy).
Token must have read_api scope to access pipeline information.
Architecture
Troubleshooting
"GPLAT or GITLAB_PAT environment variable not set"
Add GITLAB_PAT=your-token to the project root .env file.
Server not responding
Verify the .env file exists and contains a valid token:
Related
CLI Tool:
packages/platform-tools/src/cli/gitlab-ci.ts- Direct CLI accessAPI Library:
packages/platform-tools/src/lib/ci/gitlab-api.ts- Underlying API wrapperDocumentation:
.claude/instructions/mcp-tools-usage.md- MCP usage guide
Last Updated: 2025-12-09 Created By: The Collective Purpose: Enable AI agents to monitor GitLab CI/CD pipelines efficiently