gitlab_get_merge_request_discussions

Retrieve threaded discussions and replies from GitLab merge requests to streamline code review processes and track feedback efficiently.

Instructions

Get MR discussion threads Returns: Threaded discussions with replies Use when: Reading code review comments Better than notes: Shows thread structure

Example response: [{ "id": "abc123...", "notes": [{ "body": "Should we use a different approach here?", "author": {"username": "reviewer"}, "resolvable": true, "resolved": false }, { "body": "Good point, let me refactor this.", "author": {"username": "author"} }] }]

Related tools:

gitlab_resolve_discussion: Mark resolved
gitlab_add_merge_request_comment: Reply

Input Schema

Name	Required	Description
`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
`page`	No	Page number for pagination Type: integer Range: ≥1 Default: 1 Example: 3 (to get the third page of results) Note: Use with per_page to navigate large result sets
`per_page`	No	Number of results per page Type: integer Range: 1-100 Default: 20 Example: 50 (for faster browsing) Tip: Use smaller values (10-20) for detailed operations, larger (50-100) for listing
`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": {
    "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"
    },
    "page": {
      "default": 1,
      "description": "Page number for pagination\nType: integer\nRange: ≥1\nDefault: 1\nExample: 3 (to get the third page of results)\nNote: Use with per_page to navigate large result sets",
      "minimum": 1,
      "type": "integer"
    },
    "per_page": {
      "default": 50,
      "description": "Number of results per page\nType: integer\nRange: 1-100\nDefault: 20\nExample: 50 (for faster browsing)\nTip: Use smaller values (10-20) for detailed operations, larger (50-100) for listing",
      "maximum": 100,
      "minimum": 1,
      "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"
  ],
  "type": "object"
}

MCP GitLab Server