GitLab MCP Server
Let your coding agent open issues, merge requests, and CI pipelines on GitLab without leaving the chat.
Overview
GitLab MCP Server is a MCP server for the Build phase that lets agents manage GitLab projects, issues, merge requests, pipelines, and repositories via authenticated HTTP tools.
What is this MCP server?
- Manage GitLab projects, repositories, and admin settings from MCP tool calls
- Create and triage issues and merge requests with agent-driven workflows
- Inspect and trigger pipeline status for ship-ready feedback loops
- Works with gitlab.com or self-hosted via GITLAB-URL plus PRIVATE-TOKEN
- Hosted streamable-http remote at gitlab-mcp-server.fly.dev for quick registration
- Hosted remote URL: https://gitlab-mcp-server.fly.dev/
- Required headers: PRIVATE-TOKEN and GITLAB-URL on public multi-tenant host
- Supports streamable-http MCP transport per server.schema.json
Community signal: 9 GitHub stars.
What problem does it solve?
Switching between your agent and GitLab’s UI to file issues, review MRs, and check pipelines breaks flow when you ship alone.
Who is it for?
Indie builders on GitLab who want agent-assisted issue triage, MR drafts, and pipeline checks from Claude Code or Cursor.
Skip if: Teams on GitHub-only workflows or builders who never use GitLab for hosting or CI.
What do I get? / Deliverables
Your agent can read and act on GitLab projects, issues, MRs, and pipelines in one session using your token and instance URL.
- Agent-driven GitLab issue and MR operations from your IDE
- Pipeline and repository visibility inside agent workflows
- Registered MCP remote pointing at your GitLab tenant
Recommended MCP Servers
Journey fit
GitLab is where solo builders host repos and run pipelines while the product is being built and wired to delivery. Issue and MR workflows sit in integrations—connecting your agent to the same GitLab instance you deploy from.
How it compares
GitLab API MCP bridge, not a local git skill or generic code-review checklist.
Common Questions / FAQ
Who is GitLab MCP Server for?
Solo builders and small teams who use GitLab for repos and CI and want their AI coding agent to manage issues, merge requests, and pipelines through MCP.
When should I use GitLab MCP Server?
Use it during build and ship when you want the agent to create issues, update MRs, inspect pipelines, or adjust project settings without opening GitLab in the browser.
How do I add GitLab MCP Server to my agent?
Register the streamable-http remote (e.g. https://gitlab-mcp-server.fly.dev/), set PRIVATE-TOKEN to a glpat-scoped token and GITLAB-URL to your instance, then enable the server in Claude Code, Cursor, or another MCP-compatible client.