Skip to main content
Glama
DrBoria

md-gitlab-mcp

by DrBoria
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to md-gitlab-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-gitlab

      vish288
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for the GitLab REST API providing tools to manage projects, merge requests, pipelines, CI/CD variables, approvals, issues, and code reviews.
      5,395 PyPI
      6
      MIT

    • gitlab-mcp

      EllGree
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for interacting with GitLab API, supporting both self-hosted instances and gitlab.com. Provides tools for managing issues, merge requests, code review, pipelines, milestones, releases, search, and file access.
      392 npm
      MIT

    • gitlab-mcp

      kirti12025
      A
      license
      Not graded
      quality
      B
      maintenance
      A comprehensive GitLab MCP server that enables AI clients to manage projects, merge requests, issues, pipelines, wiki, releases, tags, and milestones through multiple transports and authentication methods.
      152,999 npm
      MIT

    • GitLab MCP Server

      harshmaur
      A
      license
      C
      quality
      D
      maintenance
      An MCP server that enables communication with GitLab repositories, allowing interaction with GitLab's API to manage projects, issues, and repositories through natural language.
      45
      152,999 npm
      1
      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.3/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools target a distinct resource/action, and search/create/get/list are clearly separated. The main ambiguity is among the many merge request tools, especially get_merge_request_comments vs get_merge_request_reviews and their by_url variants, though the descriptions do help.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: search_, create_, get_, list_, update_, add_, merge_, push_, fork_. Minor quirks like merge_merge_request are still predictable.

    Tool Count2/5

    With 27 tools the set is above the threshold for a focused MCP server. The merge request surface alone accounts for over a dozen tools, making the overall tool count feel heavy and harder for an agent to navigate.

    Completeness4/5

    Core GitLab workflows are covered: repository searching/creation, file pushes, issues with comments, and a thorough merge request lifecycle including reviews, status, and rebase. Missing operations like updating MR metadata or deleting repositories are minor gaps that agents can often work around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources