GitLab

{/* Generated by scripts/generate-integration-catalog.mjs. Do not edit by hand. */}

At a glance

  • Availability: Enabled by default.
  • Authentication: OAuth 2.0.
  • Connection: A user authorizes the connection in the provider's consent screen.
  • Scopes: api, read_user, read_repository.

Credentials

Set these per environment. See Connect an integration.

These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.

VariableRequiredDescription
GITLAB_CLIENT_IDYesGitLab OAuth Application ID Docs.
GITLAB_CLIENT_SECRETYesGitLab OAuth Application Secret Docs.

Setup

  1. Choose who owns the GitLab OAuth app: On hosted Veryfront, GitLab uses the Veryfront-managed GitLab OAuth app: connect GitLab from the project's integrations and approve the GitLab consent screen, no environment variables needed. Set GITLAB_CLIENT_ID and GITLAB_CLIENT_SECRET only to use your own GitLab OAuth app, which is required for local and self-hosted runs.
  2. Create an application: In GitLab, open User settings, then Applications, and add a new application. Keep it confidential.
  3. Set the redirect URI and scopes: Select the scopes api, read_user and read_repository. Add the redirect URI of the environment that completes the flow: https://api.veryfront.com/oauth/callback/gitlab for hosted Veryfront, or your app origin followed by /api/auth/gitlab/callback for a local or self-hosted app. Set GITLAB_CLIENT_ID and GITLAB_CLIENT_SECRET from the app's credentials.
  4. Verify access: Run List Projects (read-only). It returns projects the connected user can see without changing them.

Provider notes

  • The connection requests api, read_user and read_repository. The connector calls gitlab.com; api grants read and write access to the API.
  • Tools that create, update, send or delete data are marked as writes and need write authority; the other tools are read-only.

Provider API reference.

Tools

ToolAccessDescription
List Projects<br /><code className="reference-identifier">gitlab__list_projects</code>ReadList projects
Get Project<br /><code className="reference-identifier">gitlab__get_project</code>ReadGet project
Search Issues<br /><code className="reference-identifier">gitlab__search_issues</code>ReadSearch issues
Get Issue<br /><code className="reference-identifier">gitlab__get_issue</code>ReadGet issue
Create Issue<br /><code className="reference-identifier">gitlab__create_issue</code>WriteCreate issue
Update Issue<br /><code className="reference-identifier">gitlab__update_issue</code>WriteUpdate issue
Add Issue Comment<br /><code className="reference-identifier">gitlab__add_issue_comment</code>WriteAdd issue comment
List Merge Requests<br /><code className="reference-identifier">gitlab__list_merge_requests</code>ReadList merge requests
Get Merge Request<br /><code className="reference-identifier">gitlab__get_merge_request</code>ReadGet merge request
Add Merge Request Comment<br /><code className="reference-identifier">gitlab__add_merge_request_comment</code>WriteAdd merge request comment

Verify the connection

Call a read tool such as gitlab__list_projects with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.