GitLab MCP

GitLab's own MCP server, built into GitLab. Your agent connects to it and works with your projects as you: issues, epics, tasks and other work items, merge requests and reviews, the repository, and CI/CD pipelines. It's on the Free, Premium and Ultimate tiers, on GitLab.com, GitLab Self-Managed and GitLab Dedicated. What you can do with it - Find, create and update issues, tasks, epics and other work items, link them and comment on them - List, create and update merge requests, read their diffs, commits, pipelines and conflicts, review them with diff comments, and merge them - Browse the repository: files, the file tree, branches, commits, tags and releases, and add branches and commits - Check pipelines and jobs, read job logs and artifacts, and run, retry or cancel pipelines - Search across GitLab, and list projects, groups, members and labels - With GitLab Duo Agent Platform, start and follow Duo agent sessions; on Ultimate, list and triage vulnerabilities How it connects On GitLab.com it's at https://gitlab.com/api/v4/mcp over HTTP. On GitLab Self-Managed or GitLab Dedicated, use https://<your instance>/api/v4/mcp instead. Sign-in is OAuth: the first time your agent connects, it registers itself with GitLab and you approve the request in your browser. A fine-grained personal access token with the MCP tool permission works too. Agents that only speak stdio can connect through npx mcp-remote. Good to know - On GitLab.com, access to the MCP server is on by default for top-level groups. A group Owner can turn it off under Settings, General, Permissions and group features. - Every tool checks your project and namespace permissions when it's called. - You can limit the tools it offers with the X-Gitlab-Enabled-Mcp-Server-Toolsets header: core, merge_requests, work_items, repository and ci by default, plus opt-in wikis, code_security and orbit. - GitLab asks you to guard against prompt injection: use its tools only on GitLab objects you trust.

• “List my open merge requests in gitlab-org/gitlab.”

  1. list_merge_requests
  Copy

• “Review merge request 42 and leave your findings as diff comments with a summary.”

  1. get_merge_request
  2. save_merge_request_review
  Copy

• “Get issue 42 with its related merge requests.”

  1. get_work_item