GitLab MCP Server

Created By
TheRealChrisThomasa year ago
Gitlab MCP Server
Overview

What is GitLab MCP Server?

GitLab MCP Server is a tool designed to enhance project management and file operations within the GitLab API, allowing users to automate various tasks related to GitLab projects.

How to use GitLab MCP Server?

To use the GitLab MCP Server, you can install it via NPX or globally using npm. For NPX, run npx @therealchristhomas/gitlab-mcp-server. For global installation, use npm install -g @therealchristhomas/gitlab-mcp-server followed by gitlab-mcp.

Key features of GitLab MCP Server?

  • Automatic branch creation for file operations
  • Comprehensive error handling with clear messages
  • Preservation of Git history during operations
  • Support for batch operations on files
  • Project workflow management including labels and milestones
  • Repository management capabilities
  • File operations such as create, update, and retrieve
  • Issue and merge request management

Use cases of GitLab MCP Server?

  1. Automating project management tasks in GitLab.
  2. Managing multiple projects with group milestones.
  3. Streamlining file operations and version control in GitLab repositories.

FAQ from GitLab MCP Server?

  • What is the purpose of the GitLab MCP Server?

It automates project management and file operations within GitLab, enhancing productivity.

  • Is it necessary to have a GitLab account to use this server?

Yes, a GitLab account with appropriate permissions is required to access the API.

  • Can I use it for self-hosted GitLab instances?

Yes, you can configure the API URL for self-hosted instances.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
TheRealChrisThomas
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

42 minutes ago