GitLab
Connect AI tools securely to your GitLab data
About GitLab
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- Transport
- Streamable HTTP
- Authentication
- OAuth
Setup
claude mcp add gitlab --transport http https://gitlab.com/api/v4/mcpFrequently asked questions
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. 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.
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, Codex, Cursor, or VS Code. The setup snippets on this page configure each client in one step.
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.
Which transport does the GitLab MCP server use?
GitLab exposes a Streamable HTTP endpoint, the current standard transport for the Model Context Protocol, supported by all major MCP clients.
More remote MCP servers
