How do I get a Personal Access Token (PAT) for GitLab?

Log in to GitLab, go to User Settings > Access Tokens, and you can generate a new token with the 'api' scope there.

Does this support self-hosted GitLab instances?

Yes! Simply provide your instance's root URL (e.g., https://gitlab.my-company.com) in the 'GitLab Base URL' credential field.

What is a 'Project ID' in GitLab?

A Project ID is a unique numerical identifier for your project. You can also use the URL-encoded path (e.g., 'group%2Fproject') in most tools.

Can I see pipeline failures via the agent?

Yes! Use the 'list_project_pipelines' tool to retrieve the status of all recent pipelines, allowing you to quickly identify failed builds.

GitLab MCP Server for Cursor 12 tools — connect in under 2 minutes

Name: GitLab
Availability: InStock
Author: Vinkius

docs.cursor.com/context/model-context-protocol

Built by Vinkius GDPR 12 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install GitLab and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "gitlab": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About GitLab MCP Server

Connect your GitLab instance to any AI agent to automate your DevSecOps lifecycle and project management through the Model Context Protocol (MCP). GitLab is the most comprehensive AI-powered platform for software innovation. This MCP server enables you to retrieve project metadata, manage issues, track merge requests, and monitor CI/CD pipelines directly through natural conversation.

Cursor's Agent mode turns GitLab into an in-editor superpower. Ask Cursor to generate code using live data from GitLab and it fetches, processes, and writes — all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

Key Features

Project Oversight — List all accessible projects, fetch detailed configuration metadata, and track forks across your instance.
Issue & MR Management — List issues and merge requests, track their lifecycle status, and programmatically open new issues from your chat interface.
CI/CD Visibility — Retrieve a list of pipelines for any project to monitor build and deployment health in real-time.
Repository Discovery — Access the contents of files within any repository to understand codebase structures and documentation.
Global Search — Execute powerful searches across projects, issues, and users to isolate specific development artifacts.
Identity Oversight — Access detailed profile information for the authenticated user to verify permissions and account context.
Real-time Synchronization — Keep your development and operations data accessible to your AI assistant without leaving your primary workspace.

The GitLab MCP Server exposes 12 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect GitLab to Cursor via MCP

Follow these steps to integrate the GitLab MCP Server with Cursor.

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

Save the file

Cursor will automatically detect the new MCP server

Start using GitLab

Open Agent mode in chat and ask: "Using GitLab, help me..." — 12 tools available

Why Use Cursor with the GitLab MCP Server

Cursor AI Code Editor provides unique advantages when paired with GitLab through the Model Context Protocol.

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

Cursor's Composer feature can generate entire files using real-time data fetched through MCP — no copy-pasting from external dashboards

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

GitLab + Cursor Use Cases

Practical scenarios where Cursor combined with the GitLab MCP Server delivers measurable value.

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

GitLab MCP Tools for Cursor (12)

These 12 tools become available when you connect GitLab to Cursor via MCP:

create_project_issue

Open an issue

get_my_gitlab_profile

Get user identity

get_project_details

Get project metadata

get_repository_file

Read file content

list_merge_requests

List merge requests

list_project_forks

List forks

list_project_issues

List project issues

list_project_pipelines

List CI/CD pipelines

list_visible_groups

List accessible groups

list_visible_projects

List accessible projects

search_gitlab_global

Search all GitLab

verify_api_connection

Check connection

Example Prompts for GitLab in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with GitLab immediately.

"List the last 5 open merge requests for project 'my-group/my-app'."

"Check the status of the latest pipelines for project ID '12345'."

"Search GitLab for issues containing 'security patch'."

Troubleshooting GitLab MCP Server with Cursor

Common issues when connecting GitLab to Cursor through the Vinkius, and how to resolve them.

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

GitLab + Cursor FAQ

Common questions about integrating GitLab MCP Server with Cursor.

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design — tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.