F
licenseNot graded
qualityD
maintenanceMCP server for managing GitLab repositories — merge requests, pipelines, branches, and file operations.
1
-
whose-turn-mcp
by semegi
Related Servers
Alternatives to whose-turn-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server that acts as a thin proxy over GitLab REST API v4, enabling users to list merge requests, view diffs, and leave inline comments without leaving their MCP client.1313 npmMIT
- AlicenseBqualityBmaintenanceThis MCP server connects GitLab projects and merge requests with Jira work tracking, Confluence pages, and Grafana dashboards. It provides read-only access to GitLab, Confluence, and Grafana, while Jira mutations require explicit confirmation.19MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to perform automated code reviews on GitLab merge requests, including fetching details, reading diffs, posting inline comments, managing labels, and approving or unapproving MRs.345 npmMIT
- AlicenseBqualityBmaintenanceEnables an MCP client to drive the merge-request review workflow on a self-hosted GitLab CE 11.3 instance: list and create merge requests, read per-file diffs, post comments on exact diff lines, reply to and resolve threads, and merge. It also exposes read-only helpers for projects, branches, files, users, labels, pipelines and an escape-hatch raw API call, honoring a read-only mode.3013 npmMIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for GitLab integration, written in TypeScript. This server allows you to interact with GitLab merge requests, commits, pipelines, and jobs through MCP tools.6 npmISC
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues