Backlog MCP Server

Instructions

Implementation Reference

• src/tools/addVersionMilestone.ts:65-75 (handler)

  The async handler that resolves the project ID or key and calls the Backlog API to create a new version milestone.

  handler: async ({ projectId, projectKey, ...params }) => {
    const result = resolveIdOrKey(
      'project',
      { id: projectId, key: projectKey },
      t
    );
    if (!result.ok) {
      throw result.error;
    }
    return backlog.postVersions(result.value, params);
  },

• src/tools/addVersionMilestone.ts:8-41 (schema)

  Zod input schema for the tool parameters: projectId or projectKey, name, description, startDate, releaseDueDate.

  const addVersionMilestoneSchema = buildToolSchema((t) => ({
    projectId: z
      .number()
      .optional()
      .describe(t('TOOL_ADD_VERSION_MILESTONE_PROJECT_ID', 'Project ID')),
    projectKey: z
      .string()
      .optional()
      .describe(t('TOOL_ADD_VERSION_MILESTONE_PROJECT_KEY', 'Project key')),
    name: z
      .string()
      .describe(t('TOOL_ADD_VERSION_MILESTONE_NAME', 'Version name')),
    description: z
      .string()
      .optional()
      .describe(
        t('TOOL_ADD_VERSION_MILESTONE_DESCRIPTION', 'Version description')
      ),
    startDate: z
      .string()
      .optional()
      .describe(
        t('TOOL_ADD_VERSION_MILESTONE_START_DATE', 'Start date of the version')
      ),
    releaseDueDate: z
      .string()
      .optional()
      .describe(
        t(
          'TOOL_ADD_VERSION_MILESTONE_RELEASE_DUE_DATE',
          'Release due date of the version'
        )
      ),
  }));

• src/tools/tools.ts:113-113 (registration)

  The tool is instantiated and registered within the 'issue' toolset group.

  addVersionMilestoneTool(backlog, helper),

• src/tools/tools.ts:54-54 (registration)

  Import of the addVersionMilestoneTool function.

  import { addVersionMilestoneTool } from './addVersionMilestone.js';