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 does Ferentin secure GitLab access?

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.

MCP Servers

GitLab

Manage repositories, merge requests, CI/CD pipelines, and issues across your GitLab DevOps platform from an AI agent.

MCP ServersDevOpsSource ControlCI/CD

Configure Setup guide

How it works

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

AI agentAsks for something
Ferentin policies
- OAuth 2.0 consent
- Granular scope selection
- Audit logging
GitLab MCP serverAuthorized connection
Governed resultMasked, logged, returned

What you can do with GitLab

List repos
Manage merge requests
Track issues
Read pipelines
Browse code

Overview

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.

Website Developer docs

Ferentin integration

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

Connection details

Status: GA
Integration type: Remote MCP server
Authentication: OAuth 2.0
Hosting: Vendor-hosted endpoint
Required scopes: 4

Configure Setup guide

Permissions4 scopes

mcp
openid
profile
email

Security controls3

OAuth 2.0 consent
Granular scope selection
Audit logging

Technical details

Vendor: GitLab
Endpoint: gitlab.com

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).

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 does Ferentin secure GitLab access?: 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.