Skip to main content
Glama
PMelch

gitlab-mcp

by PMelch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to gitlab-mcp

No user-submitted related servers found.

    Related Servers

    • GitLab MCP Code Review

      ffpy
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to review GitLab merge requests by fetching changes, analyzing diffs, adding comments, and managing approvals through the GitLab API. Supports complete merge request analysis, file-specific reviews, and version comparisons.
      12
      4
      MIT

    • GitLab Code Review MCP

      lininn
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to review GitLab merge requests by fetching diffs, analyzing code changes, adding comments, and managing approvals through the GitLab API. Supports comprehensive merge request analysis and version comparison for automated code review workflows.
      3
      MIT

    • GitLab MCP Server

      FitoDomik
      F
      license
      A
      quality
      C
      maintenance
      Connects AI assistants to GitLab to interact with merge requests, reviews, discussions, pipelines, and test results through natural language queries. Supports viewing MR details, responding to comments, checking test summaries, and analyzing job logs.
      12
      2
      -

    • GitLab MCP Server

      bioanywhere
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Connects AI assistants to GitLab projects, enabling natural language queries for merge requests, code reviews, test results, pipelines, and discussions. Supports viewing MR details, responding to comments, and analyzing CI/CD job logs.
      -

    • GitLab MR MCP

      kopfrechner
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with GitLab repositories, allowing them to manage merge requests and issues including listing projects, fetching MR details and diffs, adding comments, and updating MR titles and descriptions.
      28 npm
      94
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct facet of a merge request (basic info, commits, diffs, discussions, approvals, pipelines, full aggregate), so there is no overlap or ambiguity between them. The 'full' tool is comprehensive but clearly distinguished as a combined superset.

    Naming Consistency5/5

    All tools follow the exact same 'get_merge_request_*' pattern, making the naming highly predictable and consistent. The resource and action are clearly identified in every name.

    Tool Count5/5

    Seven tools is a well-scoped set for a read-only merge request inspection server. Each tool covers a meaningful data aspect without adding unnecessary clutter, and the aggregate 'full' tool reduces the need for more granular additions.

    Completeness4/5

    The server thoroughly covers all major data dimensions of an individual merge request, including a 'full' option. The only notable gap is the absence of a list/search tool to discover merge requests, which may require external context to work with.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources