Guides · devtools · Everyday developer services

GitLab project (via Stripe Projects)

A GitLab project with CI/CD, registry and more. For automation use a project access token (GitLab.com needs Premium or Ultimate) with an expiry of up to 365 days.

Researched · not yet run liveLast researched 25 October 2026 · GitLab · provider site

Researched, not yet run live. Built from the provider’s official pages (linked below). A person hasn’t walked this flow end to end yet, so check each step against the source.

Steps

Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.

  1. Sign in or create a GitLab account

    Sign in to GitLab. If you have no account yet, you create it yourself; verapli does not create accounts.

    • Guided by hand
    • Human step: You sign in

    Where: https://gitlab.com/users/sign_in

  2. Create a project

    Create a GitLab project, or run stripe projects add gitlab/project.

    • Guided by hand
    • Human step: You press submit
    • After: Sign in or create a GitLab account
  3. Create a project access token

    In the project's Settings > Access tokens choose Add new token, set name, expiry (up to 365 days), role and scopes. Save it now; it is displayed once. On GitLab.com this needs Premium or Ultimate.

    • Guided by hand
    • Human step: You press submit
    • After: Create a project

    verapli captures GITLAB_TOKEN here by plain code: encrypted in your browser, never shown to AI.

Terms and gotchas

Plain-English summary, not legal advice. Each card links its source.

Can cost moneyThe rules say

Paid tier for project tokens on GitLab.com

Project access tokens on GitLab.com require a Premium or Ultimate subscription; trials get one token. [3]

What you end up with

Env varSecretFormatWhat it is
GITLAB_TOKENsecretGitLab project access token. Env var name is a verapli convention.

Renewals

  • GitLab project access token: every 365 days (default maximum) [3]

For agents

The same entry as JSON: /api/v1/entries/gitlab/project · requirements /api/v1/requirements/gitlab/project · terms /api/v1/terms/gitlab/project.

Remote MCP (read-only, no auth)
claude mcp add --transport http verapli https://verapli.com/mcp

> "What do I need for GitLab project (via Stripe Projects), and how long will it take?"
  → tools/call requirements { "provider_id": "gitlab/project" }

Sources

  1. Stripe Projects CLI (Available providers) GitLab is listed as a Stripe Projects provider (CI/CD, observability, storage) · accessed 25 October 2026 · official
  2. projects.dev provider catalogue Catalogue service id gitlab/project · accessed 25 October 2026 · official
  3. GitLab docs - Project access tokens Settings > Access tokens > Add new token with name, expiry, role, scopes; Maintainer or Owner needed; default and max expiry 365 days; displayed once; GitLab.com requires Premium or Ultimate; trials limited to one token · accessed 25 October 2026 · official

Provider rules change. This page is generated from verapli registry version 2026.1025.316; spotted something out of date? Tell us. GitLab is not affiliated with verapli.