# merge_train — gitlab

> 4 actions
> This page as plain markdown. Index: https://mcp.jmrp.io/llms.txt

Canonical: https://mcp.jmrp.io/servers/gitlab/actions/merge_train/
Language: en
Alternate: https://mcp.jmrp.io/es/servers/gitlab/actions/merge_train/index.md
Updated: 2026-11-10T02:24:12+01:00
License: https://mcp.jmrp.io/license/

Counted against gitlab.com, which is the only host this endpoint talks to, with a token it resolves to the Ultimate tier: to use it against a self-managed instance, run the server yourself — its documentation covers that. The catalog is scoped to the token that asks, so the count moves with both its tier and its permissions: a Free token sees fewer actions, a member of a group on a paid plan sees that plan's, and administration domains only appear to tokens allowed to use them. That is why the figures differ elsewhere: the upstream project counts 872 operations on Community Edition and up to 1,099 on GitLab.com's top tier, while this deployment publishes 977 because it is OAuth-only and acts with your token, so the administration domains a non-admin account cannot call never appear. All three describe the same catalog, counted from three vantage points.

Each entry also says what a GitLab fine-grained personal access token needs to run it, as GitLab 19.5.0 declares it: every permission of one line, at one of the boundaries named. Where there are alternatives, any one is enough. What follows "Some calls also need" is needed only by the calls that send that request, and the parts of the answer GitLab serves empty to such a token are listed apart.

## Actions

### `merge_train.add` — Add Merge Request To Merge Train

Add a merge request to a merge train. Returns: the resulting merge train entries with the merge request, user, pipeline, target branch, status, and duration. See also: merge_train.get, merge_train.list_branch, merge_train.list_project.

**Required parameters:** `merge_request_iid (integer)`, `project_id (string|integer)`

**Fine-grained token:** `Merge Train Merge Request: Add` at project

### `merge_train.get` — Get Merge Request On Merge Train

_read-only_

Get the merge train status of a single merge request. Returns: the merge train entry with the merge request, user, pipeline, target branch, status, and duration. See also: merge_train.list_project, merge_train.list_branch, merge_train.add.

**Required parameters:** `merge_request_iid (integer)`, `project_id (string|integer)`

**Fine-grained token:** `Merge Train: Read` at project

### `merge_train.list_branch` — List Merge Request In Merge Train

_read-only_

List the merge requests on a merge train for a target branch. Returns: merge train entries with the merge request, user, pipeline, status, duration, and pagination metadata. See also: merge_train.list_project, merge_train.get, merge_train.add.

**Required parameters:** `project_id (string|integer)`, `target_branch (string)`

**Fine-grained token:** `Merge Train: Read` at project

### `merge_train.list_project` — List Project Merge Trains

_read-only_

List all merge trains in a project. Returns: merge train entries with the merge request, user, pipeline, target branch, status, duration, and pagination metadata. See also: merge_train.list_branch, merge_train.get, merge_train.add.

**Required parameters:** `project_id (string|integer)`

**Fine-grained token:** `Merge Train: Read` at project
