24 Connect GitLab
Connect GitLab to Claude Tag so it can read code, manage issues, comment on merge requests, and check pipelines through the GitLab API. Covers token permissions, self-managed hostnames, and how it differs from GitHub.
export const BetaNote = () => Claude Tag is in public beta. Features and behavior described here may change before general availability.;
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.
24.1 Add the connection
A personal access token from a [dedicated service account](../admins/configure-gitlab.qmd#create-a-dedicated-gitlab-account-for-claude) 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-`.
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. New threads pick up the connection on their own; in an existing thread, ask Claude to use the service by name.
| Field | Value |
|---|---|
| Personal access token | The token from GitLab, starting with glpat-. Project and group access tokens work here too; the label is the field name, not a token-type constraint. |
| Allowed websites | gitlab.com (preset). For self-managed GitLab, open the Advanced tab and add your instance’s hostname here. |
GitLab’s own guide for creating tokens is at docs.gitlab.com.
24.2 How GitLab differs from GitHub
| GitLab | GitHub | |
|---|---|---|
| Auth | A service account’s personal access token | The Claude GitHub App, installed separately |
| Referencing a project in a thread | Give Claude the full project URL; it reads it through the API | Typing owner/repo in the message auto-attaches it |
| Self-managed | Your hostname under Advanced → Allowed websites | GitHub Enterprise setup |
| Handing back changes | Manages issues and comments on merge requests through the API | Draft pull requests authored by the Claude GitHub App |
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.