GitLab MCP Server

Name: GitLab MCP Server
Author: yoda-digital

@yoda-digital

リポジトリホームページ

GitLab MCP Server について

Production-grade GitLab MCP server with 86 tools — full GitLab control from any AI agent (Claude, Cursor, Zed).

#git #gitlab #ai #mcp #llm #anthropic #modelcontextprotocol

基本情報

カテゴリ

バージョン管理

ライセンス

MIT

ランタイム

node

トランスポート

stdio

公開者

yoda-digital

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "mcp-gitlab-server": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-p",
        "3000:3000",
        "\\"
      ]
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is GitLab MCP Server?

The GitLab MCP Server is a typed, paginated, schema-validated bridge from the Model Context Protocol (MCP) to the GitLab REST API, exposing 86 tools for AI agents. It works with gitlab.com or any self-hosted GitLab instance and authenticates via personal access token, OAuth Bearer token, or read‑only mode.

How to use GitLab MCP Server?

Install and run with npx -y @yoda.digital/gitlab-mcp-server or the Docker image ghcr.io/yoda-digital/mcp-gitlab-server. Configure environment variables GITLAB_PERSONAL_ACCESS_TOKEN and GITLAB_API_URL (default https://gitlab.com/api/v4). Add the server to your MCP client config (e.g., claude_desktop_config.json) as a subprocess. For remote deployments, run the HTTP service with AUTH_MODE=oauth and front it with a gateway.

Key features of GitLab MCP Server

86 typed, paginated, schema‑validated MCP tools.
Works with GitLab SaaS and self‑hosted instances.
Authentication modes: PAT, OAuth per connection, read‑only.
Supports stdio, legacy SSE, and Streamable HTTP transports.
Read‑only mode hides all mutating tools at registration.
Docker image and Helm chart with security hardening.

Use cases of GitLab MCP Server

AI coding assistant managing merge requests, pipelines, and code reviews.
Automated CI/CD monitoring and incident response via agent workflows.
Developer querying project wikis, issues, and commit history in natural language.
Shared OAuth‑gated MCP gateway for an entire DevOps team.
Safe demo or exploration with read‑only access enforced at tool registration.

FAQ from GitLab MCP Server

How does this compare to other GitLab MCP servers?

GitLab’s built‑in MCP server offers 15 tools and requires GitLab Premium/Ultimate. zereight/gitlab-mcp has broader auth surface and more tools. mcpland/gitlab-mcp focuses on a policy‑engine. This server provides 86 tools with PAT, OAuth, and read‑only modes, and runs on any GitLab instance.

What runtime does the server require?

The server runs on Node.js (published as an npm package) or as a Docker container based on node:24-alpine. The Docker image runs as non‑root (uid 1000) with all capabilities dropped.

Can the server be used in read‑only mode?

Yes. Set GITLAB_READ_ONLY_MODE=true to filter every mutating tool out at registration time. A misbehaving agent cannot see or call write tools.

What transport protocols are supported?

Three transports: stdio (default for local clients), legacy SSE (USE_SSE=true), and Streamable HTTP (USE_STREAMABLE_HTTP=true). Streamable HTTP provides POST /mcp, GET /mcp, DELETE /mcp, and a /healthz endpoint.

How does authentication work for remote deployments?

Remote HTTP deployments must use AUTH_MODE=oauth (the server refuses to start with PAT mode on a non‑loopback bind). Each MCP connection brings its own Authorization: Bearer <token>, which the server forwards as the effective PAT for that connection.

「バージョン管理」の他のコンテンツ

Atlassian Data Center MCP

b1ff

MCP servers for the Atlassian products (Bitbucket, Confluence, JIRA) of the Data Center version

Atlassian Bitbucket MCP Server

aashari

Node.js/TypeScript MCP server for Atlassian Bitbucket. Enables AI systems (LLMs) to interact with workspaces, repositories, and pull requests via tools (list, get, comment, search). Connects AI directly to version control workflows through the standard MCP interface.

157