Skip to content
GitLab logo

GitLab MCP server

Collaboration tool for developers

GitLab is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
2
Works with
Any MCP client
Auth
OAuth 2.0
License
MIT, open source
Updated
September 2026

About the GitLab MCP server

Connect GitLab once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches GitLab and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

GitLab tools your AI can run

Once connected, your assistant can call any of these GitLab actions by asking in plain language.

  • Create Issue

    Create a project issue

    3 fields

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Triggers

GitLab events your agent can watch

These start a run the moment something happens in GitLab, so work gets picked up on its own.

  • New Project Issue Event

    Triggers on project issue events when an issue is created or when an existing issue is updated, closed, or reopened.

    2 fields

Give your assistant GitLab

Connect GitLab once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

GitLab MCP, answered.

No. That is the point of it. One Activepieces server exposes GitLab alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect GitLab in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 2 tools, including Create Issue, Custom API Call, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.