🚀 GitLab MR MCP

Created By
kopfrechnera year ago
Interact seamlessly with GitLab repositories to manage merge requests and issues. Fetch details, add comments, and streamline your code review process with ease.
Overview

What is GitLab MR MCP?

GitLab MR MCP is a Model Context Protocol (MCP) server designed to facilitate interaction with GitLab repositories, enabling users to manage merge requests and issues efficiently.

How to use GitLab MR MCP?

To use GitLab MR MCP, you can either install it automatically via Smithery or manually by cloning the repository and setting up the necessary configurations with your GitLab access token.

Key features of GitLab MR MCP?

  • List available GitLab projects
  • Fetch merge request details and comments
  • Get merge request diffs
  • Add comments to merge requests and specific lines in diffs
  • Fetch issue details

Use cases of GitLab MR MCP?

  1. Streamlining code review processes by managing merge requests.
  2. Facilitating collaboration through comments on merge requests.
  3. Automating the fetching of project and issue details for better project management.

FAQ from GitLab MR MCP?

  • What prerequisites are needed to install GitLab MR MCP?

You need Node.js, a GitLab access token with API access, and GitLab project ID(s).

  • How do I troubleshoot permissions issues?

Ensure your GitLab token has the proper scopes and that the user has access to the projects.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kopfrechner
Star
33
Language
JavaScript
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.

8 hours ago