GitLab (local) logo

GitLab (local)

Beta

A community-maintained GitLab server for projects, merge requests, issues, pipelines, wikis and releases. It is not published by GitLab.

  • Developer Tools
  • Local
Runs
On the developer's Mac
Launched with
npx
Platform
macOS
Publisher
Community (zereight)

How it works

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

It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with npx -y @zereight/mcp-gitlab.

Ferentin's endpoint agent finds GitLab (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.

  1. AI agentAsks for something
  2. Ferentin policies
  3. GitLab (local) MCP serverRuns on the developer's Mac
  4. Governed resultChecked, logged, returned

About GitLab (local)

A community-maintained GitLab server for projects, merge requests, issues, pipelines, wikis and releases. It is not published by GitLab.

Frequently asked about GitLab (local)

How do I connect GitLab (local) to Ferentin?
Enroll your Macs with the Ferentin endpoint agent, then add GitLab (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
Is the GitLab (local) integration generally available?
The GitLab (local) integration is currently beta on Ferentin.