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 VS Code Copilot 12 tools — connect in under 2 minutes

Name: GitLab
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 12 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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.

GitHub Copilot Agent mode brings GitLab data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the GitLab MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using GitLab

Ask Copilot: "Using GitLab, help me..." — 12 tools available

Why Use VS Code Copilot with the GitLab MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with GitLab through the Model Context Protocol.

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

GitLab + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the GitLab MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

GitLab MCP Tools for VS Code Copilot (12)

These 12 tools become available when you connect GitLab to VS Code Copilot 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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

Common issues when connecting GitLab to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

GitLab + VS Code Copilot FAQ

Common questions about integrating GitLab MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.