Skip to main content
Glama
prachwal

gitlab-mcp-lite

by prachwal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to gitlab-mcp-lite

No user-submitted related servers found.

    Related Servers

    • GitLab MCP Server

      maxkulish
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables project management and repository operations on GitLab through the GitLab API, including file operations, branch management, issue creation, merge requests, and repository forking with support for both GitLab.com and self-hosted instances.
      3,847 npm
      Apache 2.0

    • GitLab Deployment MCP

      gggab
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying GitLab projects, pipelines, and jobs, and triggering manual deployment jobs after user confirmation, with secure token handling and scope restrictions.
      MIT

    • mcp-gitlab

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query and manage GitLab projects, issues, merge requests, and file contents via the GitLab REST API v4.
      14 npm
      MIT

    • gitlab-mcp

      mungowang
      A
      license
      B
      quality
      B
      maintenance
      Enables an MCP client to drive the merge-request review workflow on a self-hosted GitLab CE 11.3 instance: list and create merge requests, read per-file diffs, post comments on exact diff lines, reply to and resolve threads, and merge. It also exposes read-only helpers for projects, branches, files, users, labels, pipelines and an escape-hatch raw API call, honoring a read-only mode.
      30
      5 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct GitLab resource and action: pipelines, jobs, issues, or merge requests. There is no meaningful overlap between listing jobs, playing a job, creating a pipeline, or creating an MR.

    Naming Consistency4/5

    All tools use a clear gitlab_ prefix and snake_case, mostly following resource_action ordering. Minor inconsistencies exist, such as gitlab_pipeline_jobs lacking a list verb and singular/plural mixing (issue_get vs issues_list).

    Tool Count5/5

    Nine tools is well within the appropriate range for a focused GitLab lite server. Each tool has a clear role and the set does not feel bloated.

    Completeness3/5

    The surface covers useful subsets of pipelines, jobs, issues, and merge requests, but has notable gaps: no issue create/update, no MR get/merge, and no pipeline cancel/retry. The 'lite' scope explains some omissions, but agents may still hit dead ends for common workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources