Skip to main content
Glama
godrix

@godrix/mcp-gitlab-utils

by godrix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @godrix/mcp-gitlab-utils

No user-submitted related servers found.

    Related Servers

    • 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.
      82,103 npm
      MIT

    • 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.
      1,431 PyPI
      6
      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

    • gitlab-mcp

      dragomirweb
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables AI agents to perform automated code reviews on GitLab merge requests, including fetching details, reading diffs, posting inline comments, managing labels, and approving or unapproving MRs.
      233 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 15 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose. Even related MR tools (get_merge_request, get_mr_context, get_mr_discussions, get_mr_merge_status) are well-differentiated by their descriptions and scope.

    Naming Consistency5/5

    All tools follow the consistent pattern 'gitlab_verb_noun' in snake_case, with verbs like get, list, add, control, manage, prepare, resolve, search. No mixing of conventions.

    Tool Count5/5

    With 15 tools, the set is well-scoped for a GitLab utilities server covering MR, pipeline, file, and project operations. Neither too sparse nor too overwhelming.

    Completeness4/5

    The tool surface covers core MR and pipeline workflows, file retrieval, comparison, and local repository setup. Minor gaps like lack of explicit pipeline creation or branch listing are acceptable for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources