Skip to main content
Glama
snowild

GitLab MCP Server

by snowild
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to GitLab MCP Server

No user-submitted related servers found.

    Related Servers

    • 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.
      7 npm
      2
      -

    • 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

      DevquasarX9
      A
      license
      B
      quality
      A
      maintenance
      A Model Context Protocol server for GitLab that provides AI agents structured access to projects, repositories, issues, merge requests, pipelines, and releases, with read-only defaults and operational controls.
      85
      75 npm
      1
      MIT

    • GitLab MCP Server

      masx200
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with GitLab by wrapping the REST API v4 into executable tools for repository and branch management. It supports operations like creating projects, managing branches, and retrieving user information through the Model Context Protocol.
      10 npm
      1
      ISC
    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/5.0

    Scored across 30 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific GitLab resources and actions. For example, merge request operations (approve, create, get, update, merge), pipeline operations (create, cancel, retry), and branch/commit operations are all well-separated with no overlapping functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case throughout (e.g., create_merge_request, list_pipelines, get_branch). The naming convention is perfectly uniform across all 30 tools, making them easily predictable and readable.

    Tool Count3/5

    With 30 tools, this is borderline heavy for an MCP server. While GitLab has extensive functionality, the tool count approaches the upper limit of what's typically manageable, potentially overwhelming agents despite good organization.

    Completeness5/5

    The tool surface provides comprehensive coverage of GitLab's core functionality including projects, branches, commits, merge requests, pipelines, and jobs. It offers complete CRUD/lifecycle operations for all major resources with no obvious gaps for agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources