Does GitLab MCP work with self-hosted GitLab?
Yes. You can configure it to point to any GitLab instance URL including self-hosted CE and EE.
Official GitLab MCP server for managing repositories, issues, merge requests, and CI/CD pipelines with AI.
Looking for more MCP servers? Browse the full MCP tools directory or explore more tools in Version Control.
GitLab MCP mirrors the value of GitHub MCP for teams whose development lives in GitLab rather than GitHub. It provides AI assistants with access to repositories, merge requests, issues, and CI/CD pipeline context, making it most useful for engineering teams that want to bring source control operations into their AI workflow without switching tools. Self-hosted GitLab instances add some configuration complexity but work with the same core model. Teams running GitLab.com will have the smoothest setup experience.
GitLab MCP Server is an official server maintained by the Model Context Protocol team with 120K+ installs, enabling AI assistants to interact with GitLab repositories, create and manage issues, review and merge MRs, and monitor CI/CD pipeline statuses. It works with both GitLab.com and self-hosted GitLab instances.
The teams and workflows that benefit most from this tool.
Engineering teams that use GitLab.com or self-hosted GitLab for source control and CI/CD.
Merge request review, issue triage, and pipeline inspection inside an AI workflow.
Developers who want GitLab repository context available alongside code generation.
Choose GitLab MCP Server when your team works in GitLab.com or a self-hosted GitLab instance and needs AI help with repositories, issues, merge requests, or CI/CD workflows.
Good fit
Things to watch before choosing this tool.
Self-hosted GitLab instances may require additional network and auth configuration.
Less mature than GitHub MCP in terms of community tooling and documentation.
Not useful for teams that do not use GitLab as their primary source control.
Use the following configuration as a starting point for Claude Desktop or any compatible MCP client, then replace placeholder credentials with your own values.
{"mcpServers":{"gitlab":{"command":"npx","args":["-y","@modelcontextprotocol/server-gitlab"],"env":{"GITLAB_PERSONAL_ACCESS_TOKEN":"YOUR_TOKEN","GITLAB_API_URL":"https://gitlab.com/api/v4"}}}}These setup steps cover the typical installation flow for this MCP server.
Go to gitlab.com/-/user_settings/personal_access_tokens and create a Personal Access Token
Select required scopes: api, read_api, read_user, read_repository
Add the config JSON with your token and GitLab URL to claude_desktop_config.json
Restart Claude Desktop
Ask Claude to list your projects, create an issue, or check a merge request
Supported environments for GitLab MCP Server.
Claude Desktop
Yes
Cursor
Yes
VS Code
Yes
Good fit for engineering-focused MCP clients. GitLab.com setups are simpler than self-hosted.
Common questions for GitLab MCP Server.
Yes. You can configure it to point to any GitLab instance URL including self-hosted CE and EE.
Yes. It supports creating, reviewing, approving, and merging GitLab merge requests.
Yes. It can list pipeline runs and check their status for your projects.
Yes. GitLab MCP connects to GitLab repositories and uses GitLab's API, while GitHub MCP connects to GitHub.
Yes. It is open source and free to use with any GitLab account.