gitlab_add_merge_request_comment
Add comments to GitLab merge requests for code review feedback and discussions. Supports Markdown formatting, user mentions, and slash commands.
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
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| 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 | |
| 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 | |
| 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.' |
Implementation Reference
- src/mcp_gitlab/tool_handlers.py:338-344 (handler)The core handler function that implements the tool logic: validates required parameters (mr_iid, body), auto-detects project_id if not provided, and delegates to GitLabClient.add_merge_request_comment method.def handle_add_merge_request_comment(client: GitLabClient, arguments: Optional[Dict[str, Any]]) -> Dict[str, Any]: """Handle adding a comment to a merge request""" project_id = require_project_id(client, arguments) mr_iid = require_argument(arguments, "mr_iid") body = require_argument(arguments, "body") return client.add_merge_request_comment(project_id, mr_iid, body)
- src/mcp_gitlab/server.py:607-619 (schema)MCP tool registration defining the tool name, description, and input schema (JSON Schema) for parameter validation including project_id (optional), mr_iid (int required), body (string required).types.Tool( name="gitlab_add_merge_request_comment", description=desc.DESC_ADD_MR_COMMENT, inputSchema={ "type": "object", "properties": { "project_id": {"type": "string", "description": desc.DESC_PROJECT_ID}, "mr_iid": {"type": "integer", "description": desc.DESC_MR_IID}, "body": {"type": "string", "description": desc.DESC_COMMENT_BODY} }, "required": ["mr_iid", "body"] } ),
- src/mcp_gitlab/tool_handlers.py:1049-1049 (registration)Internal TOOL_HANDLERS dictionary registration mapping the tool name constant to its handler function.TOOL_ADD_MR_COMMENT: handle_add_merge_request_comment,
- src/mcp_gitlab/constants.py:236-236 (helper)Constant defining the official tool name string used throughout the codebase for consistency.TOOL_ADD_MR_COMMENT = "gitlab_add_merge_request_comment"