Skip to main content
Glama
wisesky0

gitlab-mcp

by wisesky0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to gitlab-mcp

No user-submitted related servers found.

    Related Servers

    • GitLab MCP Server

      bioanywhere
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Connects AI assistants to GitLab projects, enabling natural language queries for merge requests, code reviews, test results, pipelines, and discussions. Supports viewing MR details, responding to comments, and analyzing CI/CD job logs.
      -

    • GitLab MCP Server

      bioanywhere
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Connects AI assistants to GitLab projects, enabling users to query merge requests, review discussions, view test results and pipelines, search by branch, and respond to comments through natural language commands.
      -

    • GitLab MCP Server

      FitoDomik
      F
      license
      A
      quality
      C
      maintenance
      Connects AI assistants to GitLab to interact with merge requests, reviews, discussions, pipelines, and test results through natural language queries. Supports viewing MR details, responding to comments, checking test summaries, and analyzing job logs.
      12
      2
      -

    • GitLab MCP

      lvhungdev
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to manage GitLab projects by providing tools for issues, milestones, and team reports through a read/write interface. Users can interact with project data using natural language directly within Claude Desktop or Claude Code.
      -
    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.1/5.0

    Scored across 37 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: groups, projects, issues, merge requests, commits, and authentication. There is no overlap; even within merge requests, tools differentiate between notes, discussions, diffs, and approvals.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., list_groups, get_project, create_issue_note). The authentication tools use a separate prefix (gitlab_auth_) but remain internally consistent.

    Tool Count4/5

    37 tools is above the typical range but justified by the breadth of GitLab's API coverage. The count is not excessive; each tool serves a clear purpose without redundancy.

    Completeness5/5

    The tool surface covers full CRUD for groups, projects, issues, and merge requests, including notes, discussions, diffs, and approvals. Commit operations and authentication are also included, leaving no obvious gaps for common workflows.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources