-
licenseA
qualityA
maintenanceMCP Server for the GitLab API, enabling project management, file operations, and more.
9
3,856 npm
90,569
MIT
gitlab-mcp-server
by yoda-digital
Related Servers
Alternatives to gitlab-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server for managing GitLab repositories — merge requests, pipelines, branches, and file operations.1-
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with GitLab API, supporting both self-hosted instances and gitlab.com. Provides tools for managing issues, merge requests, code review, pipelines, milestones, releases, search, and file access.680 npmMIT
- AlicenseNot gradedqualityAmaintenanceMCP server for interacting with GitLab API, supporting dynamic tool selection and enterprise-grade security.10MIT
- FlicenseNot gradedqualityDmaintenanceHTTP-based MCP server for GitLab API, enabling project management, issue tracking, merge requests, and file operations through natural language.-
- AlicenseNot gradedqualityDmaintenanceProduction-ready MCP server providing GitLab integration with OAuth authentication, enabling AI assistants to manage projects, issues, merge requests, branches, files, and commits across GitLab instances.MIT
TDQS
B3/5.0
Scored across 86 tools
Disambiguation4/5
Most tools follow a clear resource+action pattern, but some pairs could cause confusion: list_issue_notes vs list_issue_discussions, and list_merge_request_notes vs list_merge_request_discussions are distinct (flat vs threaded) but descriptions don't emphasize the difference. Also create_or_update_file and push_files both handle file writing, though the scope (single vs multiple) is discernible.
Naming Consistency5/5
Tool names consistently follow a verb_noun pattern throughout (create_, list_, get_, update_, delete_, etc.). Even complex operations like protect_branch, cancel_auto_merge, and rebase_merge_request follow the same predictable convention. No mixing of styles or vague verbs.
Tool Count2/5
86 tools is far beyond the 25-tool threshold the rubric flags as too many. While GitLab is a large platform think the surface could be consolidated (e.g., wiki/group/project variants could be parameterized). The count is overwhelming for an agent to navigate efficiently.
Completeness4/5
The surface is extremely comprehensive, covering projects, merge requests, issues, pipelines, wikis, groups, labels, milestones, releases, and more. Minor gaps exist: no delete issue, no delete merge request, no add/remove group members (only list), and no label deletion. Core workflows are covered, so agents can mostly work around those gaps.
Maintenance
ActivityInactive
ResponsivenessUnresponsive