@withpica/mcp-server/dist/resources/llms-primer.js

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

// Copyright (c) 2025-2026 Withpica Ltd. All rights reserved.
export const WITHPICA_PRIMER = `# PICA — Music Catalog Management Platform

PICA helps music creators and publishers manage their catalog metadata,
track royalties, and prepare works for registration with collection societies.

## Core Entities

### Work
A musical composition (song, piece, library track). The central entity.
- Has: title, ISWC, work_type (song/library/demo), genre, mood, BPM, key
- Relationships: has many credits (writers/composers), has many recordings,
  has many agreements, may have audio files, may have multimedia
- Identifiers: ISWC (global), Tunecode (PRS), CAE/IPI (writer)

### Person
A human involved in music — writer, composer, performer, producer, publisher.
- Has: name, email, IPI number, ISNI, MusicBrainz ID, PRO affiliation
- Relationships: credited on many works, may have recordings, may have agreements
- Can be enriched via: ISNI, MusicBrainz, Wikidata

### Recording
A specific audio capture of a work — the master/sound recording side.
- Has: title, ISRC, duration, artist, label
- Relationships: belongs to one work, has credits (performers/producers)
- Distinct from the work: a work is the composition, a recording is the performance

### Agreement
A contract governing rights to works — publishing, sync, distribution.
- Has: title, type, parties, dates, territory, terms
- Relationships: covers many works
- Types: publishing_admin, co_publishing, master_recording, sub_publishing,
  admin_only, distribution, library_music, production, artist_contract,
  termination, report, other

### Import Document
A canonical representation of an ingested file (royalty statement, CSV import).
- Has: source (16 formats — PROs: PRS, ASCAP, BMI, SESAC, SOCAN, APRA, GEMA, SACEM; NROs: PPL, SoundExchange, GVL; Mechanical: MCPS; Distributors: DistroKid, TuneCore, CD Baby; Revenue: YouTube Content ID), period, line items, field mappings, warnings
- Immutable snapshot of the import event — not a live view
- Use pica_import_documents_query to find them, pica_import_documents_inspect to read

## First Connection

If you're connecting to this workspace for the first time or don't know where to start,
invoke the **workspace-autopilot** prompt. It reads the workspace state and routes you
to the most valuable workflow automatically.

## Recommended Workflows

1. **Catalog audit**: pica_catalog_stats → pica_works_query({ health_filter: "needs_attention" }) → pica_works_inspect({ sections: ["completeness"] })
2. **Enrichment**: pica_enrichment_candidates → pica_resolve_work (fans out across Spotify/MLC/MusicBrainz/etc.) → pica_works_inspect (verify)
3. **Statement reconciliation**: pica_import_documents_query → pica_import_documents_inspect({ sections: ["diff"] })
4. **Duplicate cleanup**: pica_find_duplicates → review → pica_merge_duplicates
5. **Registration readiness**: pica_works_inspect({ sections: ["registration"] }) → fix gaps → pica_export_song_registration

## Key Concepts

- **Organisation**: Multi-tenant — all data scoped to one org. Never cross org boundaries.
- **PICA Score**: Composite catalog legibility index (0-100, grade A-F). Four pillars:
  identification, documentation, registration, completeness.
- **Enrichment cascade**: When an identifier is added, external sources
  (MusicBrainz, ISNI, MLC) are queried automatically to fill gaps.
- **Credits**: Work credits (writers/composers with splits) are distinct from
  recording credits (performers/producers). Different tables, different role enums.
  Work credit roles: writer, composer, arranger, lyricist, producer, performer.
  Recording credit roles: Writer, Composer, Producer, Performer (PascalCase).
`;
//# sourceMappingURL=llms-primer.js.map