TeamRetro MCP Server

Instructions

Implementation Reference

• src/features/teams/service.ts:58-64 (handler)

  The main handler function that performs the actual team creation by posting data to the /v1/teams API endpoint.

  async createTeam(data: {
    name: string;
    tags?: string[];
    members?: TeamMember[];
  }): Promise<SingleApiResponse<Team>> {
    return this.post<SingleApiResponse<Team>>("/v1/teams", data);
  }

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

  Local registration of the 'create_team' tool within the teamTools object, including inline schema, description, and wrapper handler.

  create_team: {
    schema: teamSchema.pick({
      name: true,
      tags: true,
      members: true,
    }),
    description: "Create a new team with a required name, and optional tags and members",
    handler: async (args: {
      name: string;
      tags?: string[];
      members?: TeamMember[];
    }) => createToolResponse(teamsService.createTeam(args)),
  },

• src/features/teams/tools.ts:55-59 (schema)

  Input schema for the create_team tool using Zod pick from teamSchema.

  schema: teamSchema.pick({
    name: true,
    tags: true,
    members: true,
  }),

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

  Global registration where teamTools (containing create_team) is spread into the main tools object.

    ...userTools,
    ...teamTools,
    ...teamMembersTools,
    ...actionTools,
    ...retrospectiveTools,
    ...agreementTools,
    ...healthModelTools,
    ...healthCheckTools,
  };

• src/tools.ts:36-38 (registration)

  Registers the handler for each tool (including create_team) with error handling wrapper.

  Object.entries(tools).forEach(([name, tool]) => {
    toolHandlers[name] = (args: any) => toolErrorHandlers(tool.handler, args);
  });