Skip to main content
Glama
Alosies

GitLab MCP Server

by Alosies

resolve_mr_discussion

Mark a merge request discussion as resolved to track code review progress and close feedback loops in GitLab projects.

Instructions

Mark a discussion on a merge request as resolved

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID or path
merge_request_iidYesMerge request internal ID
discussion_idYesThe ID of the discussion to resolve

Implementation Reference

  • The main handler function that executes the 'resolve_mr_discussion' tool logic by making a PUT request to the GitLab API to mark the specified discussion as resolved.
    async resolveMRDiscussion(args: ResolveMRDiscussionParams) {
      const data = await this.client.put(
        `/projects/${encodeURIComponent(args.project_id)}/merge_requests/${
          args.merge_request_iid
        }/discussions/${args.discussion_id}`,
        { resolved: true }
      );
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data, null, 2),
          },
        ],
      };
    }
  • Tool registration/definition including name, description, and input schema for 'resolve_mr_discussion'.
      name: 'resolve_mr_discussion',
      description: 'Mark a discussion on a merge request as resolved',
      inputSchema: {
        type: 'object',
        properties: {
          project_id: {
            type: 'string',
            description: 'Project ID or path',
          },
          merge_request_iid: {
            type: 'number',
            description: 'Merge request internal ID',
          },
          discussion_id: {
            type: 'string',
            description: 'The ID of the discussion to resolve',
          },
        },
        required: ['project_id', 'merge_request_iid', 'discussion_id'],
      },
    },
  • src/server.ts:227-230 (registration)
    Runtime dispatch/registration in the main server switch statement that routes tool calls to the handler.
    case "resolve_mr_discussion":
      return await this.mergeRequestHandlers.resolveMRDiscussion(
        args as unknown as ResolveMRDiscussionParams
      );
  • TypeScript interface defining the input parameters for the resolve_mr_discussion handler.
    export interface ResolveMRDiscussionParams {
      project_id: string;
      merge_request_iid: number;
      discussion_id: string;
      resolved?: boolean;
    }
  • MCP input schema for validating tool arguments.
      inputSchema: {
        type: 'object',
        properties: {
          project_id: {
            type: 'string',
            description: 'Project ID or path',
          },
          merge_request_iid: {
            type: 'number',
            description: 'Merge request internal ID',
          },
          discussion_id: {
            type: 'string',
            description: 'The ID of the discussion to resolve',
          },
        },
        required: ['project_id', 'merge_request_iid', 'discussion_id'],
      },
    },

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Alosies/gitlab-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server