@withpica/mcp-server
Version:
MCP Server for withPICA — enables AI assistants to interact with your withPICA music catalog
27 lines • 1.77 kB
JavaScript
// Copyright (c) 2025-2026 Withpica Ltd. All rights reserved.
export function buildCustodyHints(work) {
const w = (work ?? {});
const hints = [];
if (w.composition_custody_source === "entry_default") {
hints.push({
gap: "custody_unclaimed_composition",
severity: "important",
suggestion: "Who holds the publishing (composition) rights? PICA has your catalogue as custodian by default because you entered this song — if that is right there is nothing to claim (pica_custody_claim refuses a chain you already hold). If someone else (publisher, co-writer) holds it, invite them via pica_collaborators_invite and let them claim custody on acceptance.",
});
}
if (w.master_custody_source === "entry_default") {
hints.push({
gap: "custody_unclaimed_master",
severity: "important",
suggestion: "Who holds the recording (master) rights? Label, distributor, self-released? Record the owner on the recording itself with pica_recording_custody_assign (e.g. transfer_type 'full_transfer', percentage 100, the artist's global creator id) — pica_custody_claim cannot do this, it refuses a chain your catalogue already holds. If a label holds it, invite the rightsholder.",
});
}
// Always fire the split hint — we never know splits from a single work row.
hints.push({
gap: "rights_share_unknown",
severity: "nice_to_have",
suggestion: "Is the publishing 100% yours or split with co-writers? If split, add co-writers via pica_credit_add with their percentage shares so the splits sum to 100. Then invite them via pica_collaborators_invite to confirm.",
});
return hints;
}
//# sourceMappingURL=custody-hints.js.map