GitLab

Replaces the archived @modelcontextprotocol/server-gitlab. @zereight/mcp-gitlab is the most actively maintained GitLab option on npm as of early 2026 and is the one most downstream clients pin against. What it does: - Full CRUD on issues, merge requests, comments, and discussions - Pipeline list, trigger, cancel, and per-job log retrieval - Wiki page read and write, with version history - Project, group, and user search with pagination - Authenticates via PAT, OAuth bearer, or per-request token passed in a header - Speaks stdio, SSE, and Streamable HTTP transports for hosted or local deploys Example: Pair with a release agent. The agent pulls the milestone, lists open MRs targeting the release branch, inspects failing pipelines, and writes a release-readiness comment on the milestone — all in one conversation. Setup: GITLAB_TOKEN and GITLAB_API_URL env vars. Set GITLAB_API_URL to https://gitlab.com/api/v4 for SaaS or to your self-hosted instance's API URL. The token needs api scope for writes and read_api for read-only workflows. Transport: stdio for local use. HTTP and SSE are supported for hosted deployments — useful when you want a single shared MCP endpoint behind a VPN rather than per-developer installs. Notes: Works against gitlab.com, self-hosted Community Edition, and Enterprise Edition. The project is a single-maintainer community effort; pin a specific version and test upgrades rather than tracking latest, because occasional breaking renames have shipped between minor versions.