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

Name: GitLab
Availability: InStock
Author: Vinkius

microsoft.github.io/autogen/docs/tools/mcp-tools

Built by Vinkius GDPR 12 Tools Framework

Microsoft AutoGen enables multi-agent conversations where agents negotiate, delegate, and execute tasks collaboratively. Add GitLab as an MCP tool provider through the Vinkius and every agent in the group can access live data and take action.

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.

python

import asyncio
from autogen_agentchat.agents import AssistantAgent
from autogen_ext.tools.mcp import McpWorkbench

async def main():
    # Your Vinkius token — get it at cloud.vinkius.com
    async with McpWorkbench(
        server_params={"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"},
        transport="streamable_http",
    ) as workbench:
        tools = await workbench.list_tools()
        agent = AssistantAgent(
            name="gitlab_agent",
            tools=tools,
            system_message=(
                "You help users with GitLab. "
                "12 tools available."
            ),
        )
        print(f"Agent ready with {len(tools)} tools")

asyncio.run(main())

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.

AutoGen enables multi-agent conversations where agents negotiate, delegate, and collaboratively use GitLab tools. Connect 12 tools through the Vinkius and assign role-based access — a data analyst queries while a reviewer validates, with optional human-in-the-loop approval for sensitive operations.

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 AutoGen 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 AutoGen via MCP

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

Install AutoGen

Run pip install "autogen-ext[mcp]"

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Integrate into workflow

Use the agent in your AutoGen multi-agent orchestration

Explore tools

The workbench discovers 12 tools from GitLab automatically

Why Use AutoGen with the GitLab MCP Server

AutoGen provides unique advantages when paired with GitLab through the Model Context Protocol.

Multi-agent conversations: multiple AutoGen agents discuss, delegate, and collaboratively use GitLab tools to solve complex tasks

Role-based architecture lets you assign GitLab tool access to specific agents — a data analyst queries while a reviewer validates

Human-in-the-loop support: agents can pause for human approval before executing sensitive GitLab tool calls

Code execution sandbox: AutoGen agents can write and run code that processes GitLab tool responses in an isolated environment

GitLab + AutoGen Use Cases

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

Collaborative analysis: one agent queries GitLab while another validates results and a third generates the final report

Automated review pipelines: a researcher agent fetches data from GitLab, a critic agent evaluates quality, and a writer produces the output

Interactive planning: agents negotiate task allocation using GitLab data to make informed decisions about resource distribution

Code generation with live data: an AutoGen coder agent writes scripts that process GitLab responses in a sandboxed execution environment

GitLab MCP Tools for AutoGen (12)

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

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

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

McpWorkbench not found

Install: pip install "autogen-ext[mcp]"

GitLab + AutoGen FAQ

Common questions about integrating GitLab MCP Server with AutoGen.

How does AutoGen connect to MCP servers?

Create an MCP tool adapter and assign it to one or more agents in the group chat. AutoGen agents can then call GitLab tools during their conversation turns.

Can different agents have different MCP tool access?

Yes. AutoGen's role-based architecture lets you assign specific MCP tools to specific agents, so a querying agent has different capabilities than a reviewing agent.