Skip to main content
Connections are added inside an Access bundle. At claude.ai/admin-settings/claude-tag, open Access bundles in the left navigation, click into a bundle (or Create one), and go to its Credentials tab.
Connecting GitLab lets Claude read and search projects, manage issues, comment on merge requests, and check pipeline status, all through the GitLab REST API. The connection is a single access token added to a bundle.
This page is the credential field reference. The full setup walkthrough, including creating a dedicated GitLab service account for Claude and scoping its group access, is at Configure GitLab access.
If your plugin marketplace includes a GitLab plugin, pair it with this connection so Claude knows how to call the API. See Attach plugins. The connection works without it.

​
Add the connection

1

Create the token in GitLab

A personal access token from a dedicated service account is recommended, so one identity covers every group you add it to. Project and group access tokens also work if you only need a single project or group. Grant the api scope for read and write, or read_api for read-only. The token starts with glpat-.
2

Add the credential to a bundle

On the bundle’s Credentials tab, click Connect next to GitLab and paste the token. For self-managed GitLab, switch to the form’s Advanced tab and add your instance’s hostname under Allowed websites.
You’ll see: GitLab listed in the bundle’s connections, and @Claude what can you access from this channel? returns it in a new thread under the bundle’s scope. GitLab’s own guide for creating tokens is at docs.gitlab.com.

​
How GitLab differs from GitHub

The token is auto-injected on every API request to your GitLab host. The model and the sandbox are not given the key; see how Agent Proxy works.