UNPKG

@withpica/mcp-server

Version:

MCP Server for withPICA — enables AI assistants to interact with your withPICA music catalog

20 lines • 1.1 kB
/** * Closed catalog vocabularies the MCP tool schemas advertise, one copy each. * * `WORK_TYPE_VALUES` mirrors the `works_work_type_check` CHECK constraint. * Before ops dfa810f8 (2026-09-28) the list was typed out three times in * this package and a fourth time, one value short, in the app's * `lib/services/catalog-enums.ts` — so pica_works_bulk_update and * pica_works_create offered `instrumental` while pica_works_update's route * refused it. * * Kept equal to the app constant by * `lib/services/__tests__/catalog-enums.test.ts` ("the MCP tools advertise * exactly WORK_TYPE_VALUES"); the app constant is pinned to the live CHECK by * the weekly constraint-parity sweep (`lib/config/constraint-parity.ts`). * The MCP package cannot import the app's module (it ships to npm on its own), * so it holds its own copy and the test ties the two together. */ export declare const WORK_TYPE_VALUES: readonly ["song", "instrumental", "library", "demo", "sample", "score"]; export type WorkTypeValue = (typeof WORK_TYPE_VALUES)[number]; //# sourceMappingURL=catalog-enums.d.ts.map