gitlab_resolve_discussion

Resolve a GitLab merge request discussion thread by marking it as resolved when code review feedback is addressed. Requires the discussion ID and merge request number for targeted action.

Instructions

Resolve a discussion thread Returns: Updated discussion Use when: Code review feedback addressed Required: Discussion ID from get_discussions

Related tools:

gitlab_get_merge_request_discussions: Find discussions
gitlab_add_merge_request_comment: Add resolution comment

Input Schema

Name	Required	Description
`discussion_id`	Yes	Discussion thread ID Type: string Required: Yes Format: SHA-like identifier How to get: From gitlab_get_merge_request_discussions Example: '6a9c1750b37d513a43987b574953fceb50b03ce7' Use case: Resolve specific discussion thread
`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": {
    "discussion_id": {
      "description": "Discussion thread ID\nType: string\nRequired: Yes\nFormat: SHA-like identifier\nHow to get: From gitlab_get_merge_request_discussions\nExample: '6a9c1750b37d513a43987b574953fceb50b03ce7'\nUse case: Resolve specific discussion thread",
      "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",
    "discussion_id"
  ],
  "type": "object"
}

MCP GitLab Server

gitlab_resolve_discussion

Instructions

Input Schema

Input Schema (JSON Schema)

Other Tools from MCP GitLab Server

Related Tools

MCP directory API