Gitlab
Give your agent GitLab project, merge request, group, and CI/CD pipeline control when GitLab is your source of truth.
Overview
com.mcparmory/gitlab is a Build-phase MCP server for managing GitLab projects, groups, merge requests, and CI/CD pipelines from your agent.
What is this MCP server?
- Manage GitLab projects, groups, and branches from agent sessions
- Create and track merge requests without leaving the IDE chat
- Inspect and drive CI/CD pipeline status for faster fix loops
- Version 1.0.3 via uvx mcparmory-gitlab or Docker ghcr.io/mcparmory/gitlab:1.0.3
- Complements ship-phase review when MRs and pipeline gates block deploy
- Server version 1.0.3
- 2 distribution packages (PyPI and OCI ghcr.io/mcparmory/gitlab:1.0.3)
- stdio MCP transport
Community signal: 25 GitHub stars.
What problem does it solve?
GitLab MR and pipeline troubleshooting fragments your attention when the agent cannot see project state or trigger pipeline-aware actions.
Who is it for?
Solo builders on GitLab.com or self-managed GitLab who want MCP-driven MR and CI operations next to their code edits.
Skip if: GitHub-only shops or teams without API tokens allowed on GitLab.
What do I get? / Deliverables
Your agent can read and act on GitLab projects and pipelines so build and ship blockers surface and resolve in one workflow.
- Agent-visible GitLab project, MR, and pipeline state for planning fixes
- Repeatable MCP-driven GitLab operations documented in your session history
Recommended MCP Servers
Journey fit
GitLab-centric indies implement features and pipeline changes together; the build integrations shelf is where host-specific DevOps bridges belong in the journey. This server talks to GitLab’s APIs for projects, MRs, and pipelines—classic third-party integration work during product construction.
How it compares
GitLab API MCP bridge, not a generic git CLI skill or standalone CI YAML linter.
Common Questions / FAQ
Who is com.mcparmory/gitlab for?
Developers and indie teams whose code and CI live on GitLab and who want agent-side control of projects, MRs, and pipelines.
When should I use com.mcparmory/gitlab?
Use it while building and shipping when you need the agent to list branches, manage merge requests, or check pipeline status on GitLab.
How do I add com.mcparmory/gitlab to my agent?
Configure stdio MCP to run mcparmory-gitlab 1.0.3 with uvx or the Docker image ghcr.io/mcparmory/gitlab:1.0.3, set GITLAB_TOKEN (or equivalent) with required scopes, and enable the server in your agent.