GitLab MCP Server (@zereight/mcp-gitlab)
A GitLab MCP server with 261 tools for projects, merge requests, issues, pipelines, wikis and releases.
Sources and review
Checked against public documentation on . Suitability guidance is our editorial judgment; this is not a performance benchmark or an endorsement.
Teams on GitLab.com or self-managed GitLab who want agents to review merge requests and manage issues.
About GitLab MCP Server (@zereight/mcp-gitlab)
@zereight/mcp-gitlab is a community GitLab MCP server tuned for agent workflows. It manages projects, merge requests, issues, pipelines, wikis, releases, tags and milestones over stdio, SSE or streamable HTTP, starts with a small toolset and activates more of its 261 tools at runtime, and supports personal access tokens, OAuth, read-only mode and remote multi-user authorization.
GitLab MCP Server (@zereight/mcp-gitlab) is listed in this index written primarily in TypeScript, with 2.1k stars on GitHub. Its latest recorded repository push was in November 2026; that is not an ASE editorial review date.
Before connecting: access and data
This record's specific permissions have not been reviewed by ASE. Read the publisher's documentation before copying setup or connecting.
- List the accounts, files and services the enabled tools can read, change or execute. Check your actual credentials and discovered tools.
- Use narrowly scoped credentials and read-only mode where supported. Review proposed writes before approving them; a generated configuration does not apply these limits for you.
- Local launch is not local-only data processing. External services receive requests, and your client may pass tool results to its model provider. Check both destinations before sharing private data.
- Keep keys and browser session files out of shared config, repositories and screenshots. Know how to disconnect the server and separately revoke its credentials or account sessions.
npm install -g @zereight/mcp-gitlab