agentpluginsdirectory
jmrplens avatar

gitlab-mcp-server

v3.3.0

by jmrplens · author: Jose M. Requena Plens

GitLab MCP server exposing up to 1093 self-managed GitLab REST/GraphQL MCP tools, or 1099 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).

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 · Open the README on GitHub

Skills
0
MCP servers
1
Stars
45
License
MIT
Repo created
2026-04-11
Last pushed
2026-10-21
Publisher type
User
Version
3.3.0

Links

MCP servers · 1

gitlabstdio
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. We list environment variable names, never values.

Category

Integrations & APIs. Assigned by this directory. Agent Plugins 1.0.0 has no category field, so no manifest declares one.

Keywords

mcp · gitlab · model-context-protocol · ai · llm · devops · ci-cd · merge-requests · issues · pipelines · code-review · graphql · rest-api

Related by publisher and keywords

  • aws-agents-for-devsecopsaws

    Investigate incidents, review code and execute UAT for release readiness, scan code for vulnerabilities, and run penetration tests with AWS DevOps Agent and AWS Security Agent.

  • tadeumendonca-skillstedeuxx

    The knowledge layer of a public agent-harness reference: 19 dense, opinionated engineering skills covering AWS infrastructure, React/Vite frontends, BFF-on-Lambda backends, CI/CD, the development loop and its quality gates. Written project-agnostically with <project> / <apex-domain> placeholders. This Power ships skills only: the harness's personas, permission hooks, typed commands and merge gates are deliberately not exported.

  • arize-phoenixArize-ai

    Connect to your Phoenix instance to debug, evaluate, and improve LLM applications.

  • aws-agentsaws

    Build, deploy, and operate AI agents on AWS. Skills for scaffolding agents with Amazon Bedrock AgentCore (Strands, LangGraph), connecting tools via Gateway and MCP, multi-agent and A2A orchestration, memory, Cedar policies, evaluation, observability, debugging traces and logs, and production hardening.

  • perplexityperplexityai

    Real-time web search, reasoning, and research through Perplexity's API

  • jev-reviewNiazMorshed2007

    An iterative, local-first software-quality score loop for AI coding agents, powered by Jev.

Add the verified badge to your README[![Verified by AgentPluginsDirectory.com against Schema 1.0.0](https://agentpluginsdirectory.com/badge.svg)](https://agentpluginsdirectory.com/plugins/gitlab-mcp-server)

✓ Verified . We fetched the manifest from GitHub and checked it against the official Agent Plugins 1.0.0 schema at agent-plugins.org.