GitLab MCP Server

io.github.jmrplens由 GitHub 帳號 jmrplens 發布v3.4.0更新於 Oct 31, 2026

Go MCP server for GitLab: 2 dynamic tools reach ~876 actions on Free/CE, up to ~1103 on Ultimate.

發布方自己的服務:Gitlab

已驗證Streamable HTTP可網頁執行效率與工作流開發者工具

概覽

AI 產生的概覽

GitLab MCP 伺服器,透過兩個探索工具存取數百個 GitLab 動作,涵蓋專案、合併請求、議題、流水線與發布。

可以做什麼
  • 搜尋本機動作目錄,取得動作 ID、參數結構與範例
  • 依標準 ID 執行 GitLab 動作:專案、群組、成員與上傳
  • 處理合併請求、議題、分支、標籤、提交、檔案與 Wiki 頁面
  • 建立發布、發佈套件並連結發布附件
  • 訂閱單一資源的變更通知,不必反覆輪詢
適用情境
適合讓助理直接操作 GitLab 執行個體:審查合併請求、處理議題、排查流水線失敗、管理分支與檔案或發佈版本;支援 GitLab.com 與自架執行個體,涵蓋 Free 到 Ultimate。
執行需求
需要具備 api 或 read_api 權限的 GitLab 個人、專案或群組存取權杖,透過 GITLAB_TOKEN 傳入;自架執行個體需設定 GITLAB_URL。可作為本機程序執行(npm、PyPI、NuGet、Homebrew、winget、Docker 或桌面擴充功能),也可使用帶 OAuth 的託管 HTTP 端點。需能連線至 GitLab 執行個體。
安裝前請注意
權杖擁有其權限範圍內的全部能力,除非啟用 GITLAB_MCP_READ_ONLY 或 GITLAB_MCP_SAFE_MODE,否則可執行寫入、刪除等破壞性動作;破壞性動作需 confirm=true。託管端點 mcp.jmrp.io 會接收你的權杖與所有請求,若要保護憑證請自行部署。上傳與下載動作會在設定的目錄內讀寫本機檔案。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 GitLab MCP Server,將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.jmrplens%2Fgitlab-mcp-server/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

{
  "mcpServers": {
    "gitlab": {
      "type": "http",
      "url": "https://mcp.jmrp.io/gitlab"
    }
  }
}

README

[GitLab MCP Server: GitLab for your AI assistant, one action catalog, three MCP tool surfaces]

GitLab MCP Server

All of GitLab for your AI assistant. Up to 1,103 actions over GitLab's REST and GraphQL APIs, from Free to Ultimate and on GitLab.com, in one self-contained binary that works with Claude, Cursor, VS Code, Codex and any other MCP client. You ask in plain language; it does the GitLab work.

11,396 tokens of startup context by default, the same on every GitLab tier (1,994 with GITLAB_MCP_CAPABILITY_SURFACE=minimal). Two tools reach the whole catalog, where listing every tool as its own costs from 558,319 to 715,378 tokens. Measured with the cl100k_base tokenizer and checked in CI. How it is measured

"Review merge request !15: is it safe to merge?" · "Why did the last pipeline fail?" · "List open issues assigned to me" · "Generate release notes from v1.0 to v2.0"

Why this server

  • Every tier and every instance. Free/CE, Premium and Ultimate, self-managed or GitLab.com with its Orbit knowledge graph. The tier is detected and the catalog follows it.
  • The token you already have. A personal, project or group access token with api, or read_api for the actions GitLab accepts from it; a fine-grained token, judged action by action from its grant; OAuth in HTTP mode. Each action's tool reference entry says which scope and which fine-grained permissions it needs.
  • Guard rails. Read-only mode, safe mode (a preview of each write instead of the write), tools excluded by name, and a confirmation before anything destructive.
  • Three surfaces, two transports. Two discovery tools by default, one tool per domain or one per action; stdio for a desktop client, or HTTP for a shared deployment that keeps each credential apart. 45 resources and 37 prompts besides.
  • Releases you can verify. Signed checksums, an SBOM per binary and build provenance for every artifact.

Install

The buttons register the Docker image, so they need Docker; the Claude Desktop row downloads a native extension instead. Create a personal access token with the api scope (or read_api for the actions GitLab accepts from it; add GITLAB_MCP_READ_ONLY=true when nothing may be written).

ClientOne-click buttonToken step
VS Code[Install in VS Code] [Install in VS Code Insiders]prompts you (masked)
Cursor[Install in Cursor]edit YOUR_GITLAB_TOKEN
LM Studio[Add to LM Studio]edit YOUR_GITLAB_TOKEN
Kiro[Add to Kiro]edit YOUR_GITLAB_TOKEN
Claude Desktop[Download the .mcpb extension]settings UI

Claude Code. The registration command never carries the token: -e GITLAB_TOKEN forwards it from the environment Claude Code hands docker.

bash
export GITLAB_TOKEN=glpat-xxxxclaude mcp add gitlab --transport stdio \  -- docker run -i --rm -e GITLAB_TOKEN ghcr.io/jmrplens/gitlab-mcp-server:latest

Any other client runs one of these as the server's command, with GITLAB_TOKEN in the environment it passes:

bash
npx -y @jmrp.io/gitlab-mcp-server                   # npm, nothing installed firstuvx jmrplens-gitlab-mcp-server                      # PyPI, nothing installed firstdnx gitlab-mcp-server                               # NuGet (.NET 10 SDK), nothing installed firstbrew install jmrplens/tap/gitlab-mcp-server         # Homebrew, macOS and Linuxwinget install --id jmrplens.gitlab-mcp-server -e   # winget, Windowsdocker run -i --rm -e GITLAB_TOKEN ghcr.io/jmrplens/gitlab-mcp-server:latest

For a self-managed instance, set GITLAB_URL=https://gitlab.example.com beside the token; with the Docker image, also forward it by adding -e GITLAB_URL to the docker arguments, since the container receives only the variables named there (Docker install). Every channel, per-client configuration and verification step is in the installation guide, and an assistant installing it for you will find the same in llms.txt.

To try it first, a public instance runs at https://mcp.jmrp.io/gitlab, and the browser inspector calls it read-only after an OAuth sign-in. Your token and every request pass through that machine, so run it yourself to keep using it; the hosted endpoint page says what it is and is not.

Documentation

Everything else is at docs.jmrp.io/gitlab-mcp-server, in English and Spanish: getting started, configuration, tool surfaces, HTTP server mode, security, privacy and troubleshooting.

Packages and listings

Contributing, security and licence

Contributions are welcome here on GitHub; CONTRIBUTING.md describes the workflow and how a change is reviewed, and CODE_OF_CONDUCT.md applies. GOVERNANCE.md says how decisions are made and who holds which role, and the roadmap says where the project is going. Report a vulnerability privately, as SECURITY.md describes. The server is MIT licensed (LICENSE).


Maintained by José M. Requena Plens · Project page · Hosted instance: mcp.jmrp.io/gitlab

來源:README.md,提交 a8c79c8

工具

2

gitlab_execute_action

GitLab Execute Action

Execute one GitLab catalog action by canonical ID or alias. Always pass params as an object. Destructive actions require top-level confirm=true. Use find first only when action or params are unclear. Example: {"action":"issue.list","params":{"project_id":"group/project"}}

輸入參數action必填params必填confirm

gitlab_find_action

GitLab Find Action

Search the local GitLab action catalog. Read-only and no GitLab API call. Use when the action ID or params are unclear. Returns schemas, hints, destructive flags, and execute examples. Example: {"query":"issue list"}

輸入參數limitquery必填explain

版本歷史

5
  1. v3.4.0最新Oct 31, 2026
  2. v3.3.0Oct 20, 2026
  3. v3.2.0Oct 9, 2026
  4. v3.1.0Oct 1, 2026
  5. v3.0.0Sep 16, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Gitlab 整合