MCP.so
Sign In

GitLab MCP Server

@GitLab

Basic information

Transport

Streamable HTTP

Authentication

OAuth

Category

Version Control

Author

GitLab

About GitLab MCP Server

GitLab connects AI tools securely to repository, issue, merge request, and DevSecOps data. Its connector gives assistants GitLab project context for understanding code work, collaboration, security workflows, and delivery status.

Connection details

https://gitlab.com/api/v4/mcp

Setup

claude mcp add gitlab --transport http https://gitlab.com/api/v4/mcp

GitLab MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

This server requires authentication. Tool discovery may require signing in or credentials from the provider.

Fetch the live tool list directly from this server's endpoint using the button above.

Frequently asked questions

1

What is the GitLab remote MCP server?

The GitLab remote MCP server is a hosted Model Context Protocol endpoint at https://gitlab.com/api/v4/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the GitLab MCP server?

Add the endpoint https://gitlab.com/api/v4/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the GitLab MCP server require authentication?

Yes. GitLab uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

4

Which transport does the GitLab MCP server use?

GitLab exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments