Skip to main content
Glama
skmprb

GitLab MCP Server

by skmprb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to GitLab MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP GitLab Server

      Vijay-Duke
      A
      license
      A
      quality
      B
      maintenance
      Enables comprehensive GitLab integration allowing LLMs to manage projects, issues, merge requests, repository files, CI/CD pipelines, and perform batch operations. Supports advanced features like AI-optimized summaries, smart diffs, and atomic operations with rollback support.
      72
      2
      Apache 2.0

    • 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 MR MCP

      kevinlin
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with GitLab repositories, manage merge requests, review code diffs, post comments, and handle issues directly through natural language.
      33 npm
      MIT

    • GitLab MR MCP

      kopfrechner
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with GitLab repositories, allowing them to manage merge requests and issues including listing projects, fetching MR details and diffs, adding comments, and updating MR titles and descriptions.
      33 npm
      94
      MIT

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

    Scored across 54 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but there is some overlap: create_commit can also create/update/delete files, making it redundant with create_file, update_file, and delete_file. Additionally, close_issue duplicates functionality available via update_issue with state_event. These overlaps could cause misselection, though descriptions help clarify.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., archive_project, get_project_issues, create_merge_request). The only slight redundancy is 'merge_merge_request', but it still adheres to the pattern. Naming is predictable and clear.

    Tool Count3/5

    With 54 tools, the server covers a wide range of GitLab operations but feels heavy. Several tools are niche (e.g., list_starred_projects, clone_group_repositories) or redundant, suggesting the set could be trimmed. A count of 20-30 would be more appropriate for the scope.

    Completeness3/5

    Core CRUD operations for projects, issues, branches, tags, files, merge requests, and pipelines are present. However, notable gaps exist: no way to comment on issues or merge requests, no update/close for merge requests, and no creation of project hooks. These missing features limit agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources