GitLab MCP Server for Claude

Content

The GitLab MCP server connects Claude and other MCP-compatible tools directly to GitLab through the GitLab API endpoint at /api/v4/mcp. It is designed for teams that want AI assistants to inspect GitLab project information, retrieve issues and merge requests, inspect CI/CD pipelines and job logs, search labels and code, and perform selected GitLab actions through OAuth-authorized access.

GitLab's MCP server is a beta GitLab Duo feature for Premium and Ultimate tiers on GitLab.com, GitLab Self-Managed, and GitLab Dedicated. It supports OAuth 2.0 Dynamic Client Registration, so compatible clients can register with the GitLab instance, open a browser authorization flow, and receive an access token for the approved GitLab scope. HTTP transport is the recommended setup path; stdio clients can use mcp-remote as a proxy.

Features

• HTTP MCP endpoint at https://gitlab.com/api/v4/mcp or the equivalent self-managed GitLab instance URL.
• OAuth 2.0 Dynamic Client Registration for first-time client setup.
• Claude Code HTTP setup with claude mcp add --transport http.
• Claude Desktop, Continue, and Zed setup through npx -y mcp-remote.
• Optional tool-name prefixing with X-Gitlab-Mcp-Server-Tool-Name-Prefix.
• Issue creation and issue lookup.
• Merge request creation, lookup, commit listing, diff retrieval, and pipeline lookup.
• CI/CD pipeline job listing, job log retrieval, and pipeline management.
• Work item note creation and retrieval.
• Global, group, and project search across scopes such as issues, merge requests, and projects.
• Label search and semantic code search for relevant code snippets.

Use Cases

• Ask Claude to inspect a GitLab issue and summarize related merge requests before starting implementation.
• Review merge request diffs, commits, and pipeline status without switching out of the coding session.
• Pull failing CI job logs and summarize likely failure causes.
• Search issues or merge requests across a group for prior art before filing a duplicate.
• Use semantic code search to find relevant implementation examples inside a GitLab project.
• Draft an issue or merge request only after a human approves the exact action.

Installation

Claude Code

1. Confirm GitLab Duo, beta features, and MCP server access are enabled for the target GitLab group or instance.
2. Add the GitLab MCP server:

claude mcp add --transport http GitLab https://gitlab.com/api/v4/mcp

1. Start Claude Code:

claude

1. Type /mcp, select the GitLab server, and complete the browser OAuth authorization flow.
2. Verify the connection with /mcp, then start with a read-only prompt.

Claude Desktop

1. Confirm Node.js 20 or later and npx are available.
2. Add the mcp-remote configuration below to the Claude Desktop MCP config.
3. Restart Claude Desktop.
4. Complete the browser OAuth authorization flow on first connect.

Configuration

HTTP transport

{
  "mcpServers": {
    "GitLab": {
      "type": "http",
      "url": "https://gitlab.com/api/v4/mcp"
    }
  }
}

HTTP transport with tool prefixing

{
  "mcpServers": {
    "GitLab": {
      "type": "http",
      "url": "https://gitlab.com/api/v4/mcp",
      "headers": {
        "X-Gitlab-Mcp-Server-Tool-Name-Prefix": "gitlab_"
      }
    }
  }
}

Claude Desktop with mcp-remote

{
  "mcpServers": {
    "GitLab": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://gitlab.com/api/v4/mcp"]
    }
  }
}

Examples

Inspect an issue before coding

Get GitLab issue 42 in project group/project, summarize the acceptance criteria, and list any linked merge requests without changing anything.

Review a merge request

Fetch merge request 15 from group/project, summarize the changed files, pipeline status, and unresolved risks.

Debug a CI failure

Get the jobs for the latest failed pipeline in group/project and summarize the relevant job log lines.

Search for related work

Search GitLab issues for "flaky login test" in group/project and return likely duplicates or related fixes.

Use semantic code search

Use semantic code search in group/project to find where authorization decisions are implemented.

Source notes

• GitLab's official documentation describes the GitLab MCP server as a beta GitLab Duo feature for Premium and Ultimate tiers on GitLab.com, GitLab Self-Managed, and GitLab Dedicated.
• The setup guide states that the server lets AI assistants such as Claude Desktop, Claude Code, Cursor, and other MCP-compatible tools access GitLab data and perform actions on behalf of the authenticated user.
• GitLab documents OAuth 2.0 Dynamic Client Registration, where the client registers as an OAuth application, requests authorization, and receives an access token.
• The recommended HTTP configuration points to https://<gitlab.example.com>/api/v4/mcp, with GitLab.com using https://gitlab.com/api/v4/mcp.
• GitLab documents Claude Code setup with claude mcp add --transport http GitLab https://<gitlab.example.com>/api/v4/mcp and Claude Desktop setup through npx -y mcp-remote.
• The tools reference lists issue, merge request, pipeline, work item note, search, label, and semantic code search tools, including write-capable tools such as create_issue, create_merge_request, create_workitem_note, and manage_pipeline.

Duplicate check

Checked current content/mcp/, content/tools/, guides, skills, agents, open pull requests, and repository-wide content for GitLab MCP, GitLab Duo MCP, /api/v4/mcp, gitlab.com/api/v4/mcp, mcp-remote GitLab, oauth_dynamic_client_registration, create_merge_request, get_merge_request, semantic_code_search, GitLab issue tracking, and self-hosted git platform MCP. Existing GitHub, Jira, Azure DevOps, and generic MCP server content do not duplicate GitLab's native MCP server for GitLab.com and self-managed GitLab instances. No dedicated GitLab MCP entry, GitLab MCP source URL duplicate, or open duplicate PR was found.

Disclosure

Editorial listing. No paid placement or affiliate link is used.