GitLab logo

GitLab

Generally Available

After OAuth2 authorization, an agent can browse projects and files, open and review merge requests, triage issues, and inspect pipeline status.

  • DevOps
  • Source Control
  • CI/CD
Authentication
OAuth 2.0
Hosting
Vendor-hosted endpoint
Required scopes
4

How it works

Every agent request passes through Ferentin policy before it reaches GitLab.

  1. AI agentAsks for something
  2. Ferentin policies
    • OAuth 2.0 consent
    • Granular scope selection
    • Audit logging
  3. GitLab MCP serverAuthorized connection
  4. Governed resultMasked, logged, returned

What you can do with GitLab

  • List repos
  • Manage merge requests
  • Track issues
  • Read pipelines
  • Browse code

Permissions requested

The OAuth 2.0 scopes GitLab asks you to approve when you connect.

ScopeAccess
mcpNot rated
openidNot rated
profileNot rated
emailNot rated

Before you connect

  • Beta feature — introduced experimental in GitLab 18.3, promoted to Beta in 18.6.
  • OAuth scopes: 'mcp' grants MCP access; openid/profile/email carry identity. PKCE (S256) and refresh tokens are supported.
  • Tools include: create/get issues, create/get merge requests (commits, diffs, pipelines), manage pipelines, get pipeline jobs and job logs, create/get work-item notes, search, search_labels, and semantic_code_search.
  • The tool catalog populates on first live connection (tools/list against the upstream).

About GitLab

GitLab is an end-to-end DevOps platform that unifies source code management, merge requests, issue tracking, and CI/CD pipelines in a single application.

Frequently asked about GitLab

What can AI agents do with GitLab through Ferentin?
Through Ferentin, agents can use GitLab for list repos, manage merge requests, track issues, read pipelines and browse code. Every call is checked against your Ferentin policies first.
How is GitLab access secured?
Requests through the GitLab integration are covered by OAuth 2.0 consent, granular scope selection and audit logging. These controls are applied by Ferentin, not by GitLab, so they hold across every connected agent.
What permissions does the GitLab integration require?
The GitLab integration requests 4 OAuth 2.0 scopes: mcp; openid; profile; email
How do I connect GitLab to Ferentin?
Open the Ferentin admin console, add GitLab as a new connection and authenticate with OAuth 2.0. You then choose which permissions and which tools your agents may use, and the connection goes live for everyone covered by your policies.
Is the GitLab integration generally available?
Yes. The GitLab integration is generally available on Ferentin, including the free tier.