gitlab_add_merge_request_comment
Add comments to GitLab merge requests for code reviews or discussions. Supports Markdown, mentions, and slash commands to streamline feedback and collaboration within the MCP GitLab Server.
Instructions
Add comment to merge request Returns: Created comment object Use when: Code review feedback, discussions Supports: Markdown, mentions, slash commands
Example: "LGTM! 👍 Just one minor suggestion..."
Related tools:
gitlab_get_merge_request_notes: Read existing
gitlab_get_merge_request_discussions: Threaded view
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | Comment content Type: string Required: Yes Format: GitLab Flavored Markdown Features: - Mentions: @username - References: #123, !456 - Code blocks: ```language - Task lists: - [ ] Task - Slash commands: /assign @user Examples: 'LGTM! 👍' 'Found an issue in line 42: ```python # This could be None result = data["key"] ``` Should check if key exists first.' | |
| mr_iid | Yes | Merge 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_id | No | Project 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 |
Input Schema (JSON Schema)
{
"properties": {
"body": {
"description": "Comment content\nType: string\nRequired: Yes\nFormat: GitLab Flavored Markdown\nFeatures:\n - Mentions: @username\n - References: #123, !456\n - Code blocks: ```language\n - Task lists: - [ ] Task\n - Slash commands: /assign @user\nExamples:\n 'LGTM! 👍'\n \n 'Found an issue in line 42:\n ```python\n # This could be None\n result = data[\"key\"]\n ```\n Should check if key exists first.'",
"type": "string"
},
"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"
}
},
"required": [
"mr_iid",
"body"
],
"type": "object"
}