mcp-gitlab MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is mcp-gitlab MCP Server?

The mcp-gitlab MCP Server is a GitLab integration server built on the Model Context Protocol (MCP) framework, providing various GitLab RESTful API tools for integration with platforms like Claude and Smithery.

how to use mcp-gitlab MCP Server?

To use the mcp-gitlab MCP Server, install the dependencies, build the project, and start the server. Configure the environment variables for GitLab API URL and access token.

key features of mcp-gitlab MCP Server?

  • GitlabSearchUserProjectsTool: Search for users and their active projects by username.
  • GitlabGetUserTasksTool: Retrieve the current user's to-do tasks.
  • GitlabSearchProjectDetailsTool: Search for project details.
  • GitlabCreateMRCommentTool: Add comments to merge requests.
  • GitlabAcceptMRTool: Accept and merge merge requests.
  • GitlabUpdateMRTool: Update the assignee, reviewer, title, description, and labels of a merge request.
  • GitlabCreateMRTool: Create new merge requests with assignee and reviewers.
  • GitlabRawApiTool: Custom calls to any GitLab API.

use cases of mcp-gitlab MCP Server?

  1. Automating GitLab project management tasks.
  2. Integrating GitLab functionalities into other applications.
  3. Enhancing collaboration through automated merge request handling.

FAQ from mcp-gitlab MCP Server?

  • What is the purpose of the mcp-gitlab MCP Server?

It serves as a bridge for integrating GitLab functionalities into various platforms using the MCP framework.

  • Is there documentation available for the tools?

Yes, detailed usage examples can be found in the USAGE.md file.

  • What programming language is used for this project?

The project is developed in TypeScript.

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

Recommend Servers

View All
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.

a day ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago