@yoda-digital
Basic information
Production-grade GitLab MCP server with 86 tools — full GitLab control from any AI agent (Claude, Cursor, Zed).
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"mcp-gitlab-server": {
"command": "docker",
"args": [
"run",
"--rm",
"-p",
"3000:3000",
"\\"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
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.
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.
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.
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.
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.
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.
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.
A server that integrates Linear's project management system with the Model Context Protocol (MCP) to allow LLMs to interact with Linear.
The system of record for AI-written software. A persistent graph of entities, relationships, changes, and provenance, so humans and AI agents see what a change touches before it merges. Beside Git today.
Model Context Protocol Servers
Interact seamlessly with GitLab repositories to manage merge requests and issues. Fetch details, add comments, and streamline your code review process with ease.
Bitbucket MCP - A Model Context Protocol (MCP) server for integrating with Bitbucket Cloud and Server APIs
Comments