gitlab-mcp-server and gitlab-mcp
These two tools are competitors, as both aim to provide a TypeScript-based MCP server for integrating with the GitLab API, offering similar functionalities for managing GitLab resources.
About gitlab-mcp-server
Alosies/gitlab-mcp-server
A fully-typed TypeScript MCP server for comprehensive GitLab API integration with Claude Desktop. Manage projects, issues, merge requests, CI/CD pipelines, and job logs with advanced features for large-scale DevOps workflows.
Implements the Model Context Protocol (MCP) as a stdio-based server, enabling Claude Desktop to execute GitLab operations through natural language queries while maintaining full TypeScript type safety across all API interactions. Supports advanced merge request workflows including threaded discussions, inline code comments, and review state management, plus self-hosted GitLab instances via configurable base URLs. Architecture uses environment-based configuration for token authentication and optional configuration files for extended setup.
About gitlab-mcp
mcpland/gitlab-mcp
A MCP server for GitLab with powerful, safe, policy-controlled access
Exposes 80+ tools across GitLab resources (MRs with code-context analysis, pipelines, wikis, releases, file management) via stdio or Streamable HTTP transports with flexible auth (OAuth 2.0 PKCE, PAT, remote token scripts, cookie-based). Enforces granular access control through read-only mode, tool allowlists/denylists, and project-scoped restrictions, while supporting enterprise networking (proxy, custom CAs, multi-instance rotation) and multiple output formats with size limits.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work