Skip to main content
Glama
Sign In
mcp-gitlab-crunchtools

mcp-gitlab-crunchtools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-gitlab-crunchtools

No user-submitted related servers found.

    Related Servers

    • GitLab MCP Server

      LoindP
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with GitLab via the GitLab REST API v4, providing tools for managing projects, merge requests, issues, pipelines, and more through MCP.
      11 npm
      ISC

    • gitlab-mcp

      EllGree
      A
      license
      Not graded
      quality
      C
      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.
      729 npm
      MIT

    • gitlab-mcp-server

      kopiloto
      A
      license
      A
      quality
      D
      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
      3
      MIT

    • GitLab MCP

      shahabmosavi
      F
      license
      Not graded
      quality
      D
      maintenance
      Exposes the GitLab REST API to MCP clients for managing projects, issues, merge requests, repositories, and CI/CD pipelines. It is multi-tenant, allowing each user to authenticate with their own token and instance URL.
      -
    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

    C2.9/5.0

    Scored across 63 tools

    Disambiguation4/5

    Most tools target a distinct resource and action, and descriptions clearly distinguish closely related operations such as pipeline vs. job retry/cancel/delete. Minor overlap exists between notes and discussions on merge requests, and between current-user and user-listing tools, but an agent can generally select correctly.

    Naming Consistency4/5

    Names consistently use snake_case with a verb_noun_tool pattern, making the surface predictable. There are small inconsistencies such as `list_mr_notes_tool` using `mr` while other tools spell out `merge_request`, and occasional noun-first forms like `search_global_tool`.

    Tool Count2/5

    Sixty-three tools is very heavy for a single MCP server and risks overwhelming an agent's selection process. While GitLab is broad, the set could be better grouped or scoped into narrower servers or workflows.

    Completeness4/5

    Coverage is extensive across projects, repositories, issues, merge requests, pipelines, labels, wiki, snippets, releases, and search. Notable gaps remain, especially merging a merge request, deleting files, and full lifecycle operations for wiki pages, snippets, releases, and milestones.

    Maintenance

    ActivityActive
    ResponsivenessLimited data

    Resources