gitlab_add_issue_comment

Add comments to GitLab issues, supporting Markdown, mentions, and references. Use to provide feedback, updates, or discussions on issues. Requires issue number and comment content.

Instructions

Add comment to issue Returns: Created comment object Use when: Providing feedback, updates Supports: Markdown, mentions, references

Example: "Fixed in PR !456. Please test and confirm."

Related tools:

gitlab_get_issue: Read issue first
gitlab_list_issues: Find issues

Input Schema

Name	Required	Description
`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.'
`issue_iid`	Yes	Issue number (IID - Internal ID) Type: integer Format: Project-specific issue number (without #) Required: Yes Examples: - 123 (for issue #123) - 4567 (for issue #4567) How to find: Look at issue URL or title - URL: https://gitlab.com/group/project/-/issues/123 → use 123 - Title: "Fix login bug (#123)" → use 123 Note: This is NOT the global issue 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"
    },
    "issue_iid": {
      "description": "Issue number (IID - Internal ID)\nType: integer\nFormat: Project-specific issue number (without #)\nRequired: Yes\nExamples:\n  - 123 (for issue #123)\n  - 4567 (for issue #4567)\nHow to find: Look at issue URL or title\n  - URL: https://gitlab.com/group/project/-/issues/123 → use 123\n  - Title: \"Fix login bug (#123)\" → use 123\nNote: This is NOT the global issue 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": [
    "issue_iid",
    "body"
  ],
  "type": "object"
}

MCP GitLab Server

gitlab_add_issue_comment

Instructions

Input Schema

Input Schema (JSON Schema)

Other Tools from MCP GitLab Server

Related Tools

MCP directory API