Skip to main content
Glama
Sign In
LeonRLewis

gitlab-mcp

by LeonRLewis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to gitlab-mcp

No user-submitted related servers found.

    Related Servers

    • gitlab-mcp

      mcpland
      A
      license
      C
      quality
      B
      maintenance
      A production-ready MCP server for GitLab enabling AI assistants to read and manage GitLab projects, merge requests, issues, pipelines, wikis, releases, and more through a unified interface.
      100
      408 npm
      10
      MIT

    • gitlab-mcp

      kirti12025
      A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive GitLab MCP server that enables AI clients to manage projects, merge requests, issues, pipelines, wiki, releases, tags, and milestones through multiple transports and authentication methods.
      251,654 npm
      MIT

    • Kepler MCP GitLab Server

      ryan-rbw
      A
      license
      Not graded
      quality
      D
      maintenance
      Production-ready MCP server providing GitLab integration with OAuth authentication, enabling AI assistants to manage projects, issues, merge requests, branches, files, and commits across GitLab instances.
      MIT

    • qodev-gitlab-mcp

      qodevai
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server for GitLab integration, enabling AI assistants to manage projects, merge requests, pipelines, issues, releases, and more.
      23 PyPI
      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.7/5.0

    Scored across 20 tools

    Disambiguation5/5

    Each tool targets a distinct operation (e.g., get_job vs get_job_log vs poll_job are clearly different). No two tools have overlapping purposes; all are well-separated.

    Naming Consistency5/5

    All tools follow the consistent pattern `gitlab_verb_noun` in snake_case. Examples: gitlab_create_merge_request, gitlab_get_job_log, gitlab_trigger_pipeline. No deviations.

    Tool Count5/5

    20 tools cover a broad yet focused scope (projects, MRs, CI/CD, files, branches). Each tool serves a clear purpose without redundancy, making the set well-scoped for a GitLab integration.

    Completeness3/5

    Key operations are present (create/get/list MRs, CI triggers, job management), but missing write actions like merge/close MRs, create/update files, or manage branches. This leaves notable gaps for full lifecycle coverage.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources