Skip to main content
Glama
ProstoyVadila

GitLab MCP Server

by ProstoyVadila
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to GitLab MCP Server

No user-submitted related servers found.

    Related Servers

    • gitlab-mcp-server

      kopiloto
      A
      license
      A
      quality
      C
      maintenance
      Enables interacting with GitLab repositories, merge requests, and code through natural language using MCP. Supports authentication with personal access tokens or OAuth2, and provides tools for listing projects, reading repository code, and analyzing merge request lifetimes.
      10
      4
      MIT

    • mcp-gitlab

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query and manage GitLab projects, issues, merge requests, and file contents via the GitLab REST API v4.
      1 npm
      MIT

    • GitLab MCP Server

      CarmeloRicarte
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with GitLab for managing projects, branches, issues, and merge requests. It provides tools for searching code and performing file operations like reading and writing directly within repositories.
      15 npm
      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 19 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose. Retrieval tools for files, issues, merge requests, pipelines, and projects are separate, and specialized filters (my_*, team_*) are well-differentiated with explicit descriptions.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern (e.g., get_*, list_*, my_*). The use of 'get' for single items and 'list' for multiple is conventional and predictable.

    Tool Count4/5

    19 tools is on the higher side but still reasonable for a GitLab MCP server covering file, issue, merge request, pipeline, and project operations. The count reflects the breadth of GitLab's features without being excessive.

    Completeness2/5

    The tool set is entirely read-only, lacking any create, update, or delete operations for issues, merge requests, projects, or pipelines. This is a significant gap that prevents agents from performing common management tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources