Skip to main content
Glama

MCP GitLab Server

by Vijay-Duke

gitlab_merge_merge_request

Merge an approved GitLab merge request with options to squash commits, delete the source branch, or auto-merge after CI pipeline success. Requires approvals met, no conflicts, and CI passing if configured.

Instructions

Merge an approved merge request Returns: Merge result with commit SHA Use when: MR is approved and ready Options: Squash, delete branch, auto-merge

Prerequisites:

  • No conflicts

  • Approvals met

  • CI passing (if required)

Related tools:

  • gitlab_get_merge_request: Check merge status

  • gitlab_approve_merge_request: Add approval

  • gitlab_rebase_merge_request: Fix conflicts

Input Schema

NameRequiredDescriptionDefault
merge_commit_messageNoCustom merge commit message Type: string Optional: Yes Variables supported: - %{title}: MR title - %{description}: MR description - %{reference}: MR reference (!123) Example: 'Merge %{title} (%{reference})' Default: GitLab's default format
merge_when_pipeline_succeedsNoAuto-merge on pipeline success Type: boolean Default: false Options: - true: Merge automatically when CI passes - false: Manual merge required Requirements: Pipeline must be running Use case: Ensure CI passes before merging
mr_iidYesMerge request number (IID - Internal ID) Type: integer Format: Project-specific MR number (without !) Required: Yes Examples: - 456 (for MR !456) - 7890 (for MR !7890) How to find: Look at MR URL or title - URL: https://gitlab.com/group/project/-/merge_requests/456 → use 456 - Title: "Add new feature (!456)" → use 456 Note: This is NOT the global MR ID
project_idNoProject identifier (auto-detected if not provided) Type: integer OR string Format: numeric ID or 'namespace/project' Optional: Yes - auto-detects from current git repository Examples: - 12345 (numeric ID) - 'gitlab-org/gitlab' (namespace/project path) - 'my-group/my-subgroup/my-project' (nested groups) Note: If in a git repo with GitLab remote, this can be omitted
should_remove_source_branchNoDelete source branch after merge Type: boolean Default: false Options: - true: Delete branch after successful merge - false: Keep branch after merge Requirements: User must have permission to delete Use case: Automatic cleanup of feature branches
squashNoSquash commits on merge Type: boolean Default: Follows project settings Options: - true: Combine all commits into one - false: Keep all commits - null: Use project default Use case: Clean commit history
squash_commit_messageNoCustom squash commit message Type: string Optional: Yes Variables supported: Same as merge_commit_message Example: '%{title} (#%{reference})' Use case: Customize squashed commit message

Input Schema (JSON Schema)

{ "properties": { "merge_commit_message": { "description": "Custom merge commit message\nType: string\nOptional: Yes\nVariables supported:\n - %{title}: MR title\n - %{description}: MR description\n - %{reference}: MR reference (!123)\nExample: 'Merge %{title} (%{reference})'\nDefault: GitLab's default format", "type": "string" }, "merge_when_pipeline_succeeds": { "default": false, "description": "Auto-merge on pipeline success\nType: boolean\nDefault: false\nOptions:\n - true: Merge automatically when CI passes\n - false: Manual merge required\nRequirements: Pipeline must be running\nUse case: Ensure CI passes before merging", "type": "boolean" }, "mr_iid": { "description": "Merge request number (IID - Internal ID)\nType: integer\nFormat: Project-specific MR number (without !)\nRequired: Yes\nExamples:\n - 456 (for MR !456)\n - 7890 (for MR !7890)\nHow to find: Look at MR URL or title\n - URL: https://gitlab.com/group/project/-/merge_requests/456 → use 456\n - Title: \"Add new feature (!456)\" → use 456\nNote: This is NOT the global MR ID", "type": "integer" }, "project_id": { "description": "Project identifier (auto-detected if not provided)\nType: integer OR string\nFormat: numeric ID or 'namespace/project'\nOptional: Yes - auto-detects from current git repository\nExamples:\n - 12345 (numeric ID)\n - 'gitlab-org/gitlab' (namespace/project path)\n - 'my-group/my-subgroup/my-project' (nested groups)\nNote: If in a git repo with GitLab remote, this can be omitted", "type": "string" }, "should_remove_source_branch": { "description": "Delete source branch after merge\nType: boolean\nDefault: false\nOptions:\n - true: Delete branch after successful merge\n - false: Keep branch after merge\nRequirements: User must have permission to delete\nUse case: Automatic cleanup of feature branches", "type": "boolean" }, "squash": { "description": "Squash commits on merge\nType: boolean\nDefault: Follows project settings\nOptions:\n - true: Combine all commits into one\n - false: Keep all commits\n - null: Use project default\nUse case: Clean commit history", "type": "boolean" }, "squash_commit_message": { "description": "Custom squash commit message\nType: string\nOptional: Yes\nVariables supported: Same as merge_commit_message\nExample: '%{title} (#%{reference})'\nUse case: Customize squashed commit message", "type": "string" } }, "required": [ "mr_iid" ], "type": "object" }

Other Tools from MCP GitLab Server

Related Tools

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Vijay-Duke/mcp-gitlab'

If you have feedback or need assistance with the MCP directory API, please join our Discord server