Gitlab Mcp Server
Let your coding agent read and act on GitLab projects, issues, and merge requests from Claude Code or Cursor without leaving the chat.
Overview
GitLab MCP Server is a MCP server for the Build phase that connects AI agents to GitLab APIs via stdio using GITLAB_TOKEN.
What is this MCP server?
- Stdio npm package @dubuqingfeng/gitlab-mcp-server (v2.0.12) with required GITLAB_TOKEN and optional GITLAB_URL for self-
- Optional Lark robot webhooks (LARK_WEBHOOK_URL, LARK_SECRET_KEY) with LARK_ENABLE_NOTIFICATION toggle
- GITLAB_NOTE_MODE: gitlab_only, lark_only, or both for where agent notes land
- Model Context Protocol server aimed at AI agents operating on GitLab resources
- Catalog server version 1.0.1; npm package @dubuqingfeng/gitlab-mcp-server v2.0.12
- Transport: stdio
- Required env: GITLAB_TOKEN; optional GITLAB_URL and Lark webhook vars
Community signal: 9 GitHub stars.
What problem does it solve?
You ship on GitLab but your agent cannot see issues, MRs, or project metadata unless you copy-paste from the browser.
Who is it for?
Indie builders on GitLab (gitlab.com or self-hosted) who want agent-driven issue and project workflows with optional Lark alerts.
Skip if: Teams on GitHub-only workflows or anyone unwilling to store a GitLab PAT in local MCP config.
What do I get? / Deliverables
After registration, your agent can call GitLab-backed MCP tools with your token and optional Lark/GitLab note routing for team visibility.
- Agent-callable GitLab MCP tools over stdio
- Configurable GitLab base URL for SaaS or self-hosted
- Optional dual-path notes to GitLab and/or Lark
Recommended MCP Servers
Journey fit
GitLab is where solo builders store code and run CI; wiring it into the agent belongs on the Build shelf as a dev integration even though you also use it when reviewing and shipping. Integrations is the canonical facet for third-party VCS and DevOps MCP servers that extend the agent with repository APIs.
How it compares
MCP GitLab integration, not a standalone Claude skill or full CI replacement.
Common Questions / FAQ
Who is GitLab MCP Server for?
Solo and small-team developers using Claude Code, Cursor, or other MCP clients who keep source code and issues in GitLab.
When should I use GitLab MCP Server?
Use it during Build and Ship when you want the agent to query or update GitLab without manual copy-paste, especially alongside optional Lark notifications.
How do I add GitLab MCP Server to my agent?
Install @dubuqingfeng/gitlab-mcp-server from npm, set GITLAB_TOKEN (and GITLAB_URL if self-hosted), add the stdio server entry in your MCP config, then restart the client.