Skip to main content
Glama
DevquasarX9

gitlab-mcp-server

by DevquasarX9
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to gitlab-mcp-server

No user-submitted related servers found.

    Related Servers

    • qodev-gitlab-mcp

      qodevai
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server for GitLab integration, enabling AI assistants to manage projects, merge requests, pipelines, issues, releases, and more.
      MIT

    • GitLab MCP Server

      ZephyrDeng
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      A Model Context Protocol server that enables AI assistants to interact with GitLab repositories, allowing tasks like managing merge requests, searching projects, and creating comments through RESTful API integration.
      19 npm
      2
      -

    • GitLab MCP Server

      snowild
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to interact with self-hosted GitLab instances through 30 specialized tools. It supports managing projects, merge requests, CI/CD pipelines, and repository operations via the GitLab REST API v4.
      30
      MIT

    • gitlab-mcp

      DKeken
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server for self-hosted GitLab instances, enabling users to manage issues, merge requests, pipelines, and more via Claude Code.
      10 npm
      MIT

    • gitlab-mcp

      mcpland
      A
      license
      C
      quality
      A
      maintenance
      A production-ready MCP server for GitLab enabling AI assistants to read and manage GitLab projects, merge requests, issues, pipelines, wikis, releases, and more through a unified interface.
      100
      233 npm
      10
      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

    B3.2/5.0

    Scored across 85 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose and target resource (e.g., specific merge request, pipeline, or project aspects). Overlapping concepts like 'summarize' vs 'get' are differentiated by their descriptions, ensuring an agent can reliably select the right tool.

    Naming Consistency5/5

    All 85 tools follow a consistent 'gitlab_verb_noun' pattern in snake_case, making the set highly predictable. Verbs like get, list, search, find, trace, and summarize are used systematically across resource types.

    Tool Count4/5

    With 85 tools, the server is on the high side but appropriate for covering GitLab's extensive API surface (projects, groups, users, merge requests, pipelines, CI/CD, releases, packages, etc.). The count is justified by the breadth of the domain, though some tools could be consolidated.

    Completeness2/5

    The tool set is almost entirely read-only and analytical, lacking essential CRUD operations (e.g., no create_issue, update_merge_request, delete_project) and mutation tools (e.g., merge, run pipeline). This severely limits agents that need to perform actions, leaving significant gaps for a full GitLab interaction.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources