---
title: "gitlab-mcp-server"
description: "GitLab MCP server exposing up to 1088 self-managed GitLab REST/GraphQL MCP tools, or 1094 on GitLab.com Ultimate with Orbit. Includes a default 2-tool dynamic surface, 34 base / 51 self-managed Ultimate / 52 GitLab.com U"
canonical: https://agentpluginsdirectory.com/plugins/gitlab-mcp-server
last-updated: 2026-10-13
---

# gitlab-mcp-server
GitLab MCP server exposing up to 1088 self-managed GitLab REST/GraphQL MCP tools, or 1094 on GitLab.com Ultimate with Orbit. Includes a default 2-tool dynamic surface, 34 base / 51 self-managed Ultimate / 52 GitLab.com Ultimate meta-tools, 45 resources, 37 prompts, 18 completion types, and 4 MCP capabilities (completions, progress, elicitation, resource subscriptions).
- Slug: gitlab-mcp-server
- Publisher: Jose M. Requena Plens
- Repository: https://github.com/jmrplens/gitlab-mcp-server
- Manifest: plugin.json
- Version: 3.2.0
- License: MIT
- Category (editorial): integrations
- Skills: 0
- MCP servers: 1 (gitlab)
- Stars: 45
- Repository created: 2026-04-11
- Repository last pushed: 2026-10-13
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/gitlab-mcp-server
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What gitlab-mcp-server does, in the publisher's words

Connect your AI assistant to GitLab so it can review merge requests, triage pipelines, manage issues, and draft releases, in plain language. One static binary (or a container), 1000+ GitLab tools over the full REST + GraphQL API, working with Claude, Cursor, VS Code, and any MCP client.

You talk to your AI assistant; it does the GitLab work. No project IDs, API endpoints, or JSON to remember.

10,359 tokens of startup context by default, the same on every GitLab tier (1,694 with GITLAB_MCP_CAPABILITY_SURFACE=minimal). Two tools reach the whole catalog; measured with the cl100k_base tokenizer and verified in CI on every commit. How it is measured

- macOS: ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Linux: ~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Windows: %APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json
- Plain-language GitLab. The AI translates "is MR!15 safe to merge?" into the right API calls. You don't touch endpoints, IDs, or JSON.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/jmrplens/gitlab-mcp-server/HEAD/README.md

## MCP servers

- gitlab: transport: stdio; command: docker run -i --rm -e GITLAB_URL -e GITLAB_TOKEN -e GITLAB_MCP_SKIP_TLS_VERIFY -e GITLAB_MCP_TOOL_SURFACE -e GITLAB_MCP_CAPABILITY_SURFACE -e GITLAB_MCP_META_PARAM_SCHEMA -e GITLAB_MCP_TIER -e GITLAB_

Read from the plugin's own mcp.json. Environment variable names only, never values.