Sekora GitLab MCP

Created By
Sekora10 months ago
Complete GitLab MCP integration with 72 specialized tools for comprehensive DevOps management
Overview

A comprehensive Model Context Protocol (MCP) server for GitLab integration with Claude Desktop, providing 72 specialized tools covering every aspect of GitLab project management.

Installation

NPM Package

# For GitLab.com
npx @sekora/gitlab-mcp

# For self-hosted GitLab
GITLAB_URL="https://gitlab.company.com" GITLAB_TOKEN="your-token" npx @sekora/gitlab-mcp

Claude Desktop Configuration

{
  "mcpServers": {
    "gitlab-mcp": {
      "command": "npx",
      "args": ["@sekora/gitlab-mcp"],
      "env": {
        "GITLAB_TOKEN": "your-gitlab-private-token"
      }
    }
  }
}

Tool Categories (72 Tools - 100% Complete)

Issue Management (8 tools)

- Create, update, close, and link issues
- Milestone and label management
- Advanced filtering and search

Pipeline & Job Management (17 tools)

- Pipeline monitoring, triggering, and analytics
- Job execution, retry, and artifact management
- Real-time status monitoring

Merge Request Management (8 tools)

- Complete MR lifecycle from creation to merge
- Review comments and conflict resolution
- Approval workflows and validation

Repository Management (8 tools)

- Branch and file operations
- Commit history and tag management
- Release management with assets

Security & Quality Analysis (6 tools)

- SAST, dependency, and container scanning
- License compliance and code quality metrics
- Vulnerability assessment and remediation

Environment & Deployment (7 tools)

- Environment monitoring and feature flags
- Deployment tracking and GitLab Pages management
- Runner and variable management

Project Administration (6 tools)

- Member and permission management
- Project settings and integrations
- Webhook and access token management

Analytics & Insights (4 tools)

- Project analytics and contributor statistics
- Activity monitoring and usage metrics
- Performance trends and optimization insights

Team Collaboration (4 tools)

- Discussions and mentions management
- Wiki pages and code snippets
- Team communication workflows

Specialized Monitoring (6 tools)

- Advanced pipeline analytics and dashboards
- Success rate analysis and performance metrics
- Cross-project monitoring and alerts

Key Features

- Complete GitLab Coverage: Every major GitLab feature accessible through Claude
- Multi-Instance Support: Configure multiple GitLab instances simultaneously
- Enterprise Ready: Supports GitLab CE, Premium, and Ultimate editions
- Security First: Built-in token management and secure authentication
- Rich Analytics: Comprehensive insights and performance monitoring
- Type-Safe: Built with TypeScript and Zod validation
- Production Ready: Comprehensive error handling and validation

Requirements

- Node.js 18.19.0+
- GitLab private access token with api scope
- GitLab.com or self-hosted GitLab instance

Authentication

Create a GitLab private access token:
1. Go to GitLab → Profile → Access Tokens
2. Create token with api scope
3. Configure via environment variable or Claude Desktop config

Multi-Tenant Support

Configure multiple GitLab instances:
{
  "mcpServers": {
    "work-gitlab": {
      "command": "npx",
      "args": ["@sekora/gitlab-mcp"],
      "env": {
        "GITLAB_URL": "https://gitlab.company.com",
        "GITLAB_TOKEN": "work-token"
      }
    },
    "personal-gitlab": {
      "command": "npx",
      "args": ["@sekora/gitlab-mcp"],
      "env": {
        "GITLAB_TOKEN": "personal-token"
      }
    }
  }
}

Use Cases

- DevOps Automation: Pipeline monitoring, deployment management, environment control
- Code Review: MR creation, approval workflows, conflict resolution
- Project Management: Issue tracking, milestone planning, team coordination
- Security Operations: Vulnerability scanning, compliance monitoring, quality analysis
- Team Collaboration: Wiki management, discussions, activity monitoring
- Analytics & Reporting: Project insights, contributor analysis, performance metrics

Built with the https://mcp-framework.com for reliable, type-safe GitLab API integration.

Server Config

{
  "mcpServers": {
    "gitlab-mcp": {
      "command": "npx",
      "args": [
        "@sekora/gitlab-mcp@latest"
      ],
      "env": {
        "GITLAB_TOKEN": "your-gitlab-private-token"
      }
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
Sekora
Star
-
Category

Recommend Clients

View All
KTA-ORACLE

2 months ago
VERILEX-DATA

3 months ago
VIBE-PROSPECTING

3 months ago
HEYM

6 days ago
Chain.Love MCP
@Chain.Love

## Overview ### what is Chain.Love MCP? Chain.Love MCP is a hosted remote MCP server and gateway for AI agents. It provides a single endpoint for discovering and comparing Web3 infrastructure services across 50+ blockchain networks, including RPCs, indexing, oracles, storage, compute, and developer tools. ### how to use Chain.Love MCP? To use Chain.Love MCP, add the hosted endpoint to your MCP client and connect to `https://app.chain.love/mcp` over Streamable HTTP. For public use cases, the basic MCP server URL is enough. For private downstream MCPs, add credentials only when required using `x-chainlove-cred-<credentialKey>` headers. ### key features of Chain.Love MCP? - Hosted remote MCP gateway for AI agents - Single endpoint for Web3 infrastructure discovery across 50+ blockchain networks - Aggregates infrastructure options across RPCs, indexing, oracles, storage, compute, and developer tools - Streamable HTTP transport - Public documentation and onboarding resources available online ### use cases of Chain.Love MCP? - Discovering and comparing Web3 infrastructure providers across many blockchain networks - Finding RPC, indexing, oracle, storage, compute, and developer tooling options through one MCP server - Giving AI agents a single hosted integration surface for Web3 infrastructure discovery - Reducing the need to integrate many separate provider-specific endpoints ### FAQ from Chain.Love MCP? - Can Chain.Love MCP be used as a hosted remote MCP server? Yes. Chain.Love MCP is designed to be consumed as a hosted remote MCP endpoint at `https://app.chain.love/mcp`. - Does Chain.Love MCP require credentials? Not always. Some downstream integrations may require credentials, which can be passed using `x-chainlove-cred-<credentialKey>` headers when needed. - How do I know which credential header to use? You can check the open-source Chain.Love registry at `https://github.com/Chain-Love/chain-love/blob/main/references/offers/mcpservers.csv` or browse `https://app.chain.love/toolbox/mcpservers` and look for the relevant `credentialKey` value. - Where can I learn more? Landing page: `https://www.chain.love/mcp-gateway` Documentation: `https://chain-love.gitbook.io/mcp-module`

2 months ago
UI-THING

4 months ago
SAGE

4 months ago
SILVIA-MCP

a month ago
@ENCONVERT/MCP

a month ago