freemcplab / 디렉터리 / 플레이그라운드 / GitLab MCP

● 커뮤니티 zereight 🔑 본인 키 필요

GitLab MCP

Name: GitLab MCP MCP Server
Author: zereight

Treat GitLab like the GitHub MCP treats GitHub — issues, MRs, pipelines, comments — with explicit support for self-hosted instances.

Zereight's GitLab MCP is the de-facto community implementation. It covers REST and a curated GraphQL surface, supports self-hosted GitLab via GITLAB_API_URL, and has fine-grained read/write tool gating.

▶ 데모 보기 📦 설치 💡 사용 사례

왜 쓰나요

핵심 기능

Issues, MRs, comments, labels, milestones
Pipelines: list, retry, cancel
Repo file read/write
Self-hosted instance support
Read-only mode toggle
Group + project search

라이브 데모

실제 사용 모습

준비됨

설치

클라이언트 선택

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "gitlab-mcp-zereight": {
      "command": "npx",
      "args": [
        "-y",
        "@zereight/mcp-gitlab"
      ],
      "env": {
        "GITLAB_PERSONAL_ACCESS_TOKEN": "${GITLAB_TOKEN}",
        "GITLAB_API_URL": "https://gitlab.com/api/v4"
      }
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "gitlab-mcp-zereight": {
      "command": "npx",
      "args": [
        "-y",
        "@zereight/mcp-gitlab"
      ],
      "env": {
        "GITLAB_PERSONAL_ACCESS_TOKEN": "${GITLAB_TOKEN}",
        "GITLAB_API_URL": "https://gitlab.com/api/v4"
      }
    }
  }
}

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "gitlab-mcp-zereight": {
      "command": "npx",
      "args": [
        "-y",
        "@zereight/mcp-gitlab"
      ],
      "env": {
        "GITLAB_PERSONAL_ACCESS_TOKEN": "${GITLAB_TOKEN}",
        "GITLAB_API_URL": "https://gitlab.com/api/v4"
      }
    }
  }
}

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "gitlab-mcp-zereight": {
      "command": "npx",
      "args": [
        "-y",
        "@zereight/mcp-gitlab"
      ],
      "env": {
        "GITLAB_PERSONAL_ACCESS_TOKEN": "${GITLAB_TOKEN}",
        "GITLAB_API_URL": "https://gitlab.com/api/v4"
      }
    }
  }
}

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "gitlab-mcp-zereight",
      "command": "npx",
      "args": [
        "-y",
        "@zereight/mcp-gitlab"
      ]
    }
  ]
}

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json

{
  "context_servers": {
    "gitlab-mcp-zereight": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@zereight/mcp-gitlab"
        ]
      }
    }
  }
}

context_servers에 추가. 저장 시 Zed가 핫 리로드.

claude mcp add gitlab-mcp-zereight -- npx -y @zereight/mcp-gitlab

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: GitLab MCP

Review an MR end-to-end from Claude

👤 Developers ⏱ ~15 min intermediate

언제 쓸까: You want a quick triage pass on a teammate's MR before opening the GitLab UI.

흐름

Get MR

Fetch MR by IID; pull title, description, diffs.✓ 복사됨

→ Diff loaded
Inspect pipeline

List pipelines for this MR; report failures.✓ 복사됨

→ Pipeline status known
Comment

Post inline comments for the issues you found.✓ 복사됨

→ Comments visible in UI

결과: MR review done without leaving Claude; comments posted under your account.

Triage failing pipelines across projects

👤 Developers ⏱ ~15 min intermediate

언제 쓸까: CI is red across several projects and you want a unified view.

흐름

List failed

list_pipelines status=failed across group X.✓ 복사됨

→ Failed pipelines listed
Pull logs

For each, fetch the failing job log tail.✓ 복사됨

→ Top error per pipeline
Cluster

Group by error signature; identify the shared cause.✓ 복사됨

→ One root-cause summary

결과: You know whether it's one infra issue or N independent failures.

조합

다른 MCP와 조합해 10배 효율

gitlab-mcp-zereight + linear

Cross-link Linear issues to GitLab MRs in PR descriptions

Combine gitlab-mcp-zereight with linear: Cross-link Linear issues to GitLab MRs in PR descriptions✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출	비용
list_issues	(see docs)	List issues with filters	1 call
get_merge_request	(see docs)	Fetch MR details + diffs	1 call
create_merge_request	(see docs)	Open a new MR	1 call
list_pipelines	(see docs)	List CI pipelines	1 call
retry_pipeline	(see docs)	Retry a failed pipeline	1 call
add_comment	(see docs)	Post issue/MR comment	1 call

비용 및 제한

운영 비용

API 쿼터: GitLab API rate limits (varies by instance)
호출당 토큰: MR diffs can be huge — paginate
금액: Free; your GitLab plan applies
팁: Use read-only mode for any agent that doesn't need to write

보안

권한, 시크릿, 파급범위

최소 스코프: api read_repository (scoped PAT)

자격 증명 저장: PAT in env var

데이터 외부 송신: Your GitLab API URL only

절대 부여 금지: use sudo scope unless you know why

문제 해결

자주 발생하는 오류와 해결

401 on self-hosted

Set GITLAB_API_URL to the full /api/v4 URL of your instance

Rate limited

Use a project-scoped PAT; lower polling cadence

대안

GitLab MCP 다른 것과 비교

대안	언제 쓰나	단점/장점
Official GitLab MCP	Once GitLab ships first-party	Not yet GA
github-mcp-server	You're on GitHub	Different platform