GitLab MCP Server

Created By
Foxhunta year ago
Overview

what is GitLab MCP Server?

GitLab MCP Server is a TypeScript-based server that interacts with a self-hosted GitLab instance, allowing users to fetch and manage GitLab data such as projects, issues, and comments.

how to use GitLab MCP Server?

To use the GitLab MCP Server, install the dependencies, build the server, and configure it with your GitLab instance. You can then use various tools to interact with your GitLab data.

key features of GitLab MCP Server?

  • list_projects: Lists all projects accessible to the user.
  • get_issues: Retrieves issues for a specific project with filtering options.
  • get_issue_notes: Fetches comments for a specific issue.
  • search: Searches for projects and issues based on a term.
  • get_issue: Retrieves a specific issue using its ID.
  • get_todos: Lists to-do items with optional filters.
  • get_wiki_page: Retrieves a specific wiki page by project ID.
  • list_wiki_pages: Lists all wiki pages for a project.

use cases of GitLab MCP Server?

  1. Managing project issues and comments in a self-hosted GitLab.
  2. Automating the retrieval of project data for reporting.
  3. Integrating GitLab data with other applications or services.

FAQ from GitLab MCP Server?

  • Can I use GitLab MCP Server with any GitLab instance?

Yes! It works with any self-hosted GitLab instance.

  • Is there a way to debug the server?

Yes! You can use the MCP Inspector for debugging.

  • What programming language is used for GitLab MCP Server?

The server is built using TypeScript.

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