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.
コメント