Skip to main content
Glama
70,879 servers. Updated

Matching MCP tools:

Matching MCP Connectors:

"GitLab" matching MCP servers:

  • A
    license
    C
    quality
    B
    maintenance
    MCP server for GitLab that provides 85 tools covering issues, merge requests, repositories, CI/CD, wiki, packages, and attachments, with support for both gitlab.com and self-hosted instances. It can read attachments so models can see screenshots and other files.
    85
    684
    MIT
  • A
    license
    C
    quality
    A
    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
    684
    9
    MIT
  • A
    license
    -
    quality
    B
    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.
    92,984
    MIT
  • F
    license
    -
    quality
    C
    maintenance
    Exposes the GitLab REST API to MCP clients for managing projects, issues, merge requests, repositories, and CI/CD pipelines. It is multi-tenant, allowing each user to authenticate with their own token and instance URL.
  • A
    license
    A
    quality
    A
    maintenance
    Model Context Protocol (MCP) server for GitLab — exposes 1006 GitLab REST & GraphQL API operations as MCP tools (42 meta-tools / 57 enterprise), 24 resources, 38 prompts, and 17 completion types for AI assistants. Written in Go, single static binary, stdio and HTTP transport.
    2
    31
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Enables AI-powered exploration and interaction with GitLab instances through comprehensive search, code browsing, and repository management. Supports both self-hosted and GitLab.com with flexible authentication for read and write operations.
    63
    177
    10
    MIT
  • A
    license
    B
    quality
    C
    maintenance
    A Model Context Protocol (MCP) server for GitLab and Jira integration. This server allows AI agents like gemini-cli to interact with your GitLab and Jira instances.
    32
    12
    11
    MIT
  • F
    license
    B
    quality
    D
    maintenance
    Enables users to retrieve GitLab commit records and automatically generate daily work reports that can be sent to WeChat Work groups. Supports querying commits by date and user, with seamless enterprise messaging integration.
    3
  • A
    license
    -
    quality
    B
    maintenance
    Enables querying GitLab projects, pipelines, and jobs, and triggering manual deployment jobs after user confirmation, with secure token handling and scope restrictions.
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Enables AI assistants to review GitLab merge requests by fetching changes, analyzing diffs, adding comments, and managing approvals through the GitLab API. Supports complete merge request analysis, file-specific reviews, and version comparisons.
    12
    4
    MIT
  • A
    license
    -
    quality
    D
    maintenance
    Enables AI assistants to review GitLab merge requests by fetching diffs, analyzing code changes, adding comments, and managing approvals through the GitLab API. Supports comprehensive merge request analysis and version comparison for automated code review workflows.
    3
    MIT
  • A
    license
    B
    quality
    D
    maintenance
    GitLabとの連携機能を提供するModel Context Protocol (MCP) サーバーです。GitLabの特定のプロジェクトからパイプラインの失敗情報やマージリクエストへの指摘事項を取得し、AIアシスタントに提供します。
    3
    MIT
  • A
    license
    C
    quality
    D
    maintenance
    A MCP server that transforms code repositories from GitHub, GitLab, or local directories into LLM-friendly formats, preserving context and structure for better AI processing.
    3
    11
    Apache 2.0
  • A
    license
    -
    quality
    C
    maintenance
    MCP server for Jenkins (with optional GitLab integration) that lets AI assistants list jobs, trigger and track deployments, fetch build logs, and verify whether tickets are deployed, without touching the Jenkins UI.
    MIT