TeamRetro MCP Server

Instructions

Implementation Reference

• src/features/teams/tools.ts:37-52 (handler)

  The complete definition of the 'update_team' tool, including its Zod schema for input validation (team ID, optional name and tags), description, and handler function that calls the teamsService to perform the update.

  update_team: {
    schema: teamSchema.pick({
      id: true,
      name: true,
      tags: true
    }),
    description: "Update an existing team's details, such as its name and associated tags, by providing the team's ID",
    handler: async (args: {
      id: string;
      name?: string;
      tags?: string[];
    }) => {
      const { id, ...updateData } = args;
      return createToolResponse(teamsService.updateTeam(id, updateData));
    },
  },

• src/tools.ts:13-22 (registration)

  Registration of teamTools (which includes update_team) by spreading into the main tools object used to generate toolSchema and toolHandlers.

  const tools = {
    ...userTools,
    ...teamTools,
    ...teamMembersTools,
    ...actionTools,
    ...retrospectiveTools,
    ...agreementTools,
    ...healthModelTools,
    ...healthCheckTools,
  };

• src/features/teams/service.ts:38-50 (helper)

  The helper service method 'updateTeam' invoked by the tool handler, which performs a PATCH request to the TeamRetro API to update the team.

  /**
   * Update an existing team
   * @param teamId The ID of the team to update
   * @param data Team data to update
   * @returns Updated team object
   * @throws ErrorMCP if team not found or validation fails
   */
  async updateTeam(
    teamId: string,
    data: Partial<Pick<Team, "name" | "tags" | "members">>
  ): Promise<SingleApiResponse<Team>> {
    return this.patch<SingleApiResponse<Team>>(`/v1/teams/${teamId}`, data);
  }