gitlab-api

Guide GitLab MCP tools and glab CLI for merge requests, issues, and pipelines.

Updated Dec 24, 2025

Search Tags:#api #mcp #issues #gitlab #pipelines #merge requests #glab cli

One-click install

npx skills add https://github.com/MakotoUwaya/dotfiles --skill gitlab-api

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: gitlab-api
Source: https://github.com/MakotoUwaya/dotfiles/tree/main/.config/claude-code/skills/gitlab-api
Command: npx skills add https://github.com/MakotoUwaya/dotfiles --skill gitlab-api

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides clear guidance on using GitLab's MCP tools and the glab CLI for efficient interaction with GitLab issues, merge requests, and pipelines, helping users choose the right tool and avoid common pitfalls.

Core Features & Use Cases

Tool Selection: Differentiates when to use MCP tools versus glab CLI for various GitLab operations.
API Usage Patterns: Details how to use glab api for common tasks like creating draft notes and handling nested parameters.
Handling Limitations: Offers solutions for issues like multi-line text in descriptions and pagination.
Use Case: When creating a merge request with a detailed description including code snippets or specific formatting, this Skill guides you to use glab CLI with heredoc syntax to ensure the description is rendered correctly.

Quick Start

Use the gitlab-api skill to create a draft note on merge request 123 with the text "This looks good!".

Frequently Asked Questions about gitlab-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is the best way to manage API pagination for GitLab pipelines and issues?▼

The best way to manage GitLab API pagination is by following specific instructions provided for handling limits within the `glab` CLI. This ensures you retrieve all necessary pipeline and issue data across multiple pages efficiently.

How do I create GitLab merge requests with multi-line descriptions using the API?▼

To create GitLab merge requests with multi-line descriptions, use the `glab` CLI with heredoc syntax. This approach ensures that code snippets and specific formatting in the description are rendered correctly, bypassing MCP tool limitations with multi-line text.

When should I use GitLab MCP tools versus the glab CLI for managing pipelines and issues?▼

GitLab MCP tools and the `glab` CLI both manage GitLab operations, but they have distinct use cases. MCP tools handle standard issues and pipelines, while `glab` CLI is necessary for specific tasks like creating draft notes and handling nested JSON parameters.

How do I handle nested JSON parameters when using the glab api command?▼

To handle nested JSON parameters with the `glab api` command, use input files. This technique allows you to structure complex payloads accurately for GitLab API requests without encountering shell escaping or formatting issues.

Why does my GitLab API request fail when creating draft notes for merge request reviews?▼

GitLab API requests for draft notes fail due to limitations in multi-line text handling. To resolve this, use the `glab` CLI instead of MCP tools, which provides specific instructions for successfully creating draft notes in review workflows.

What is the best way to manage API pagination for GitLab pipelines and issues?▼