GitLab MCP Server (noqta-gitlab-server)

Created By
nooqtaa year ago
MCP Server for interacting with the GitLab API
Overview

what is GitLab MCP Server?

GitLab MCP Server is a Model Context Protocol (MCP) server designed to facilitate interaction with the GitLab API, allowing AI assistants to perform various actions on GitLab through natural language commands.

how to use GitLab MCP Server?

To use the GitLab MCP Server, clone the repository, install dependencies, configure environment variables with your GitLab Personal Access Token, and run the server either directly with Node.js or using npx after publishing to npm.

key features of GitLab MCP Server?

  • Search for GitLab projects by name.
  • Manage issues, including listing, creating, and updating them.
  • Create branches and merge requests.
  • Search for GitLab users.
  • Create new GitLab projects (repositories).

use cases of GitLab MCP Server?

  1. Automating project management tasks in GitLab.
  2. Integrating GitLab functionalities into AI assistants.
  3. Simplifying issue tracking and management through natural language commands.

FAQ from GitLab MCP Server?

  • What is required to run the GitLab MCP Server?

You need Node.js, npm, a GitLab account, and a GitLab Personal Access Token with appropriate scopes.

  • Can I use this server with self-hosted GitLab?

Yes, you can configure the server to point to your self-hosted GitLab instance.

  • Is the GitLab MCP Server open source?

Yes, it is licensed under the MIT License.

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

6 hours ago