Connect the GitLab MCP server to your Atlassian site
Connect your Atlassian site to the GitLab MCP server so your team can securely enable GitLab tools, authorize access, and use them in Atlassian. The GitLab MCP server is currently a beta GitLab feature.
Before you begin
You must be an Atlassian organization admin for the target site.
You must have access to a GitLab account to authorize the MCP server.
GitLab MCP access must be enabled before you connect it to your Atlassian site.
Enable access to the GitLab MCP server
GitLab.com
Required role: Owner of the top-level group. This setting is configured on the top-level group, not a subgroup.
In GitLab, select Search or go to and open the top-level group that owns the relevant projects.
Go to Settings → General.
Expand Permissions and group features.
Under MCP client access, select Allow connection to GitLab.
Select Save changes.
GitLab Self-Managed or GitLab Dedicated
Required role: Instance administrator.
In GitLab, open Admin.
Go to Settings → General.
Expand Visibility and access controls.
Under MCP client access, select Allow connection to GitLab.
Select Save changes.
Enabling MCP does not grant users additional access. Each user authenticates with their own GitLab identity and can access only the groups, projects, and resources they already have permission to use.
Connect the GitLab MCP server to your Atlassian site
After enabling MCP access in GitLab, follow Add an external MCP server from Atlassian Administration to connect GitLab to your site.
During setup, select the GitLab MCP server from the list. Follow the installation instructions, authenticate with your GitLab account, review the requested permissions, and select the tools you want to enable for your site.
Was this helpful?