MCP.so
ログイン

Gitlab MCP Server

@jmrplens

基本情報

カテゴリ

バージョン管理

ライセンス

MIT

トランスポート

stdio

作者

jmrplens

投稿者

José M. Requena Plens

Gitlab MCP Server について

Open source GitLab MCP server for AI assistants: 2-tool dynamic find/execute over 860+ GitLab actions (1,000+ Enterprise), stdio/HTTP/OAuth, safe/read-only modes.

Gitlab MCP Server の設定

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

{
  "mcpServers": {
    "gitlab-mcp-server-jmrplens": {
      "command": "docker",
      "args": [
        "pull",
        "ghcr.io/jmrplens/gitlab-mcp-server:latest"
      ]
    }
  }
}

Gitlab MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

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

概要

What is Gitlab MCP Server?

Gitlab MCP Server connects your AI assistant to GitLab, enabling it to review merge requests, triage pipelines, manage issues, and draft releases in plain language. It provides 1000+ GitLab tools over the full REST + GraphQL API and works with Claude, Cursor, VS Code, and any MCP client. It runs as a single static binary or a container on Windows, Linux, and macOS.

How to use Gitlab MCP Server?

Choose an installation method: one-click buttons (VS Code, Cursor, etc.), claude mcp add command, the built-in setup wizard (gitlab-mcp-server --setup), or manual JSON configuration. Provide a GitLab Personal Access Token with the api scope. For self-managed GitLab, set the GITLAB_URL environment variable. Then simply ask your AI assistant to perform GitLab tasks.

Key features of Gitlab MCP Server

  • Plain-language GitLab – the AI translates natural requests into API calls.
  • 1000+ tools covering the full GitLab platform (REST + GraphQL).
  • Low-token default dynamic surface (exposes 2 tools, reaches the full catalog).
  • Proven with real models – 99.5% aggregate success across thousands of operations.
  • Safe by design – read-only mode, safe mode (dry-run preview), and TLS options.
  • Runs anywhere – one static binary or container; amd64 & arm64; stdio and HTTP.

Use cases of Gitlab MCP Server

  • Review a merge request for safety and merge readiness.
  • Triage a failed pipeline and identify the cause.
  • List open issues assigned to a user.
  • Generate release notes from version to version.
  • List GitLab projects managed by the user.

よくある質問

1

What token is required to use Gitlab MCP Server?

A GitLab Personal Access Token with the **api** scope is needed. The token is passed via the `GITLAB_TOKEN` environment variable.

2

How do I connect to a self-managed GitLab instance?

Set the `GITLAB_URL` environment variable to your instance URL. For self-signed certificates, also set `GITLAB_SKIP_TLS_VERIFY=true`.

3

What is the default tool surface and why?

The default **dynamic** surface exposes only 2 tools (`gitlab_find_action` and `gitlab_execute_action`) while still reaching the full catalog. This keeps token consumption low and fits any client’s context window.

4

Can I run Gitlab MCP Server in read-only mode?

Yes, read-only mode is a built-in safety feature. It prevents mutations, allowing safe exploration of GitLab data.

5

Does Gitlab MCP Server support HTTP/remote deployments?

Yes, there is an HTTP server mode for shared, long-running deployments, documented in the HTTP Server Mode guide.

コメント

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