Skip to main content
Glama
rokrokss
by rokrokss

Related Servers

Alternatives to @zereight/mcp-gitlab

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query and manage GitLab projects, issues, merge requests, and file contents via the GitLab REST API v4.
      1 npm
      MIT
    • 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.
      28 npm
      94
      MIT
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to interact with GitLab repositories, monitor documentation changes, manage issues and merge requests, and search across projects with comprehensive file and commit operations.
      -
    • 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.
      28 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with GitLab for managing projects, branches, issues, and merge requests. It provides tools for searching code and performing file operations like reading and writing directly within repositories.
      4 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides tools for interacting with the GitLab API, enabling AI assistants to search repositories, manage issues, create branches, and more through natural language commands.
      14 npm
      MIT

    TDQS

    C2.6/5.0

    Scored across 115 tools

    Disambiguation2/5

    While most tools target specific resources, several boundaries are unclear: create_note overlaps with create_issue_note and create_merge_request_note, get_merge_request_diffs overlaps with list_merge_request_diffs, and get_file_contents overlaps with get_repository_tree for directory listings. The note/discussion/thread/draft family and list_issues vs my_issues also create real misselection risk.

    Naming Consistency3/5

    The core verb_noun pattern is recognizable and mostly readable, but there are notable deviations: mr_discussions and my_issues don't follow the verb pattern, get_merge_request_notes is actually a list operation, create_or_update_file bundles two verbs, and bulk_publish_draft_notes uses an adverb prefix. These inconsistencies make the set feel mixed rather than systematic.

    Tool Count1/5

    At 115 tools this is an extreme tool count for an agent-facing server, far beyond the typical well-scoped 3-15 range. Even for GitLab's broad domain, the surface is overwhelming and selection cost is high.

    Completeness3/5

    The server covers a remarkably wide surface: MRs, issues, pipelines, releases, milestones, wiki, labels, environments, and file operations. However, several lifecycle gaps remain: no delete_file, delete_branch, delete_project, or delete_merge_request, and environments/deployments are read-only. These are notable dead ends for common workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues