GitLab connector

​

Prerequisites

• A GitLab account with access to the target projects or groups
• A personal access token, group access token, or project access token with scopes such as api and read_api
• For self-managed GitLab: the REST base URL for your instance (e.g. https://gitlab.example.com/api/v4)
• project_contributor access in AgentRuntime

​

Connect in AgentRuntime

​

What you can build

• Incident → issue — Workflow failure step captures error context → LLM formats a title and body → create_issue in the on-call project.
• Release notes triage — list_issues with state=opened → LLM summarizes blockers → post summary to Slack or Notion.
• Project discovery — list_projects with search → agent picks the correct project_id_or_path for downstream API calls.
• Custom automation — gitlab_api_call for merge requests, pipelines, or labels not covered by first-class tools.

​

Tools

​

Example

{
  "id": "gitlab-issue",
  "type": "mcp_call",
  "name": "File GitLab issue",
  "tool_name": "create_issue",
  "tool_args": {
    "project_id_or_path": "my-group/my-service",
    "title": "Workflow run {{input.run_id}} failed",
    "description": "{{steps.summarize-error.result.summary}}",
    "labels": "automation,incident"
  },
  "depends_on": ["summarize-error"],
  "timeout_s": 30
}

​

Configuration

​

Troubleshooting

​

Related

• Integrations quickstart
• Connector catalog
• Troubleshooting