OpenAPI Marketplace

gitlab-developer-core-openapi

Name: gitlab-developer-core-openapi
Author: Lân Nguyễn Trịnh

v4.0.0 · 2 endpoints · 0 connections · shared by Lân Nguyễn Trịnh

Core GitLab.com REST API for listing projects, managing project issues and notes, and inspecting or starting CI/CD pipelines. This schema targets GitLab.com with a fixed HTTPS base URL; self-managed GitLab requires a separate tenant-specific schema. The user supplies a GitLab access token at connection time; no credential is included. Official documentation: https://docs.gitlab.com/api/rest/

Connect this API to an AI agent Browse all specs

What you can do with gitlab-developer-core-openapi via MCP

Every endpoint below becomes a governed tool your AI agent (Claude, ChatGPT, or a customer-facing VX agent) can call — with scoped permissions, sandbox testing, and audit logs.

Method	Path	Operation	Description
GET	`/projects`	listGitLabProjects	List accessible projects
GET	`/projects/{project_id}/issues`	listGitLabProjectIssues	List project issues

Usage guide

Getting credentials

Create or sign in to an account at GitLab.com.
Create a personal, project, or group access token with only the scopes required by the workflow, such as read_api for read-only access or api for write operations.
When VX Agent asks for authentication, provide the token in the PRIVATE-TOKEN header.

This Swagger uses the fixed GitLab.com base URL https://gitlab.com/api/v4. It does not target self-managed GitLab instances.

Keep the access token private. Do not paste it into the Swagger file, marketplace description, prompts, or chat messages.

How to use this API

Use this API to discover projects, manage project issues, add issue notes, inspect pipelines, and start CI/CD pipelines.

A typical workflow is:

Use GET /projects to find accessible projects and obtain a numeric project_id.
Use GET /projects/{project_id}/issues to list opened, closed, or filtered issues.
Use GET /projects/{project_id}/issues/{issue_iid} to inspect one issue before changing it.
Use POST /projects/{project_id}/issues to create an issue after confirming the title, description, labels, assignees, and due date.
Use PUT /projects/{project_id}/issues/{issue_iid} to update an issue or close/reopen it.
Use POST /projects/{project_id}/issues/{issue_iid}/notes to add a comment after confirming the final text.
Use GET /projects/{project_id}/pipelines to inspect CI/CD activity.
Use POST /projects/{project_id}/pipeline only after confirming the branch or tag and all variables.

Starting a pipeline may deploy code, change infrastructure, or consume CI minutes. Require explicit confirmation before starting one.

Safety and usage notes

Do not expose private repositories, issue content, CI variables, access tokens, or deployment details. Use narrow queries and pagination for large projects.

Official documentation: GitLab REST API.

How to use this spec

Create a free VX Agents account (sandbox tools included).
Open the marketplace and connect “gitlab-developer-core-openapi” to an agent.
Expose it as an MCP server for Claude/ChatGPT, or chat with it directly.