Skip to main content
Glama
wanadev

@wanadev/mcp-gitlab

by wanadev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @wanadev/mcp-gitlab

No user-submitted related servers found.

    Related Servers

    • GitLab MCP Server

      TeslaLord
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with GitLab repositories through natural language, supporting project management, issue tracking, merge requests, file access, and repository operations. Includes a conversational agent interface with structured outputs for comprehensive GitLab workflow automation.
      -

    • GitLab MCP Server

      anupsahu
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with GitLab repositories through secure OAuth 2.0 authentication. Supports comprehensive GitLab operations including merge requests, issues, file management, commits, and branch operations through natural language.
      9 npm
      MIT

    • GitLab MCP Server

      lucky-dersan
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides GitLab integration for AI assistants using Model Context Protocol, enabling repository operations, file management, issue tracking, merge requests, and branch/tag administration through natural language.
      2
      -

    • 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
      -
    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.4/5.0

    Scored across 100 tools

    Disambiguation4/5

    Most tools follow a clear resource+action pattern, so group vs project variants and note/diff/discussion tools are generally distinguishable. However, add_issue_to_epic and link_work_items explicitly overlap (the latter is described as the replacement), and list_issues/list_project_issues plus several similar work-item helpers add some ambiguity.

    Naming Consistency4/5

    The vast majority use consistent snake_case verb_noun names (list_*, get_*, create_*, update_*, close_*, delete_*). Minor inconsistencies: `mr` abbreviations vs `merge_request`, and `workitem` vs `work_item` in list_workitem_statuses, prevent a perfect score.

    Tool Count1/5

    100 tools is an extreme count for an MCP surface, far beyond typical scoped servers, and includes redundant group/project variants plus legacy/new Work Item linking (add_issue_to_epic vs link_work_items). Even though GitLab is broad, this bloated surface is expensive for agents to navigate and many tools feel duplicative rather than earning their place.

    Completeness3/5

    Core lifecycles for epics, issues, milestones, MRs, notes, labels, members, branches/files, and pipelines are well covered. Notable gaps remain: no delete issue/epic/milestone, no close/reopen/delete MR, no project member listing, no branch deletion, and no project/group creation, so agents will hit dead ends in some administrative workflows.

    Maintenance

    ActivityInactive
    ResponsivenessResponsive

    Resources