withPICA
withPICA is a music rights and catalog platform for managing works, recordings, credits, agreements, royalties, collaborators, and related assets.
Verdict
Common use cases
- Check which agreements expire this quarter
- Find all sessions a specific engineer worked on
- Pull royalty split details for a track
- Audit unsigned contributors in the catalog
- List active agreement templates for new deals
Integration
- Vendor
- withPICA
- Category
- other
- Auth
- API_KEY
- Tools
- 10
- Composio slug
withpica
Tools
- Get Current User
Return the connected withPICA user's profile and linked catalog person ID.
- Get Person
Return detailed catalog information for one person by ID.
- Get Workspace Context
Return the connected organisation, catalog counts, health summary, and current priorities.
- List Agreements
Search and filter agreements, including signature and expiry states, one page at a time.
- List Agreement Templates
Return the active and system agreement templates available to the organisation.
- List People
Search and filter people in the organisation's catalog, returning one page and a continuation cursor.
- List Projects
Return a bounded list of projects in the connected organisation.
- List Sessions
Return a bounded list of recording or creative sessions in the connected organisation.
- List Works
Return a bounded page of musical works in the organisation's catalog.
- Search Recordings
Search recordings by title, artist name, or ISRC and return one result page with recovery guidance.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Click 'Add Integration' and select withPICA from the list. 3. Open your withPICA account settings in a separate browser tab and generate a new API key with read permissions for people, agreements, projects, and sessions. 4. Copy the key and paste it into the Switchy connection dialog, then click 'Connect'. 5. Switchy will verify the key and display your connected organisation name and catalog summary. 6. Open any Project in Switchy and type '@withPICA get workspace context' to confirm the connection works — you should see your org name, catalog counts, and current priorities. 7. From there, @mention withPICA in any message to search people, list agreements, or pull session details.
What teammates see: by default, memories from withPICA are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Expiring Agreements Audit
@withPICA list all agreements expiring in the next three months. Show me the person name, agreement type, and exact expiry date for each one.
Session Credits Lookup
@withPICA find all sessions where [person name] was listed as a contributor. Include the session date, project name, and their role on each.
Unsigned Contributor Report
@withPICA list all people in the catalog who do not have a signed agreement on file. Group them by their primary role if available.
Royalty Split Breakdown
@withPICA get the agreement for [project or track name]. Show me all parties involved, their royalty percentages, and the signature status.
Template Comparison
@withPICA show me all active agreement templates. For each one, summarize what type of deal it covers and any key terms or clauses.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@withPICA list all people in our catalog who have unsigned agreements and show their contact details
Found 12 people with unsigned agreements in your catalog. Here's a summary: 5 artists awaiting master recording agreements, 4 session musicians with pending work-for-hire docs, and 3 producers missing publishing splits. Each entry includes name, email, phone, and the specific agreement template awaiting signature. The list is paginated — this shows the first 10 results with a continuation cursor for the remaining 2.
This example combines catalog search with agreement filtering, a common workflow in music rights management. Requires read access to both people and agreements. Results depend on your organization's catalog size and agreement template setup — smaller catalogs may return fewer matches.
@withPICA get our workspace health summary and flag any projects with missing metadata or expired agreements
Your workspace contains 47 active projects, 203 catalog people, and 89 agreements. Health check: 3 projects are missing producer credits, 2 recording sessions lack ISRC codes, and 5 agreements expired in the last 30 days (4 master licenses, 1 publishing split). Current organizational priorities show 'Q1 album release prep' and 'rights audit completion' as top focus areas.
Workspace context provides a high-level operational snapshot useful for rights audits or onboarding new team members. The 'health summary' field is computed by withPICA's backend — what counts as 'unhealthy' depends on your organization's configuration. No write actions occur here.
@withPICA find all recording sessions from the last quarter and draft a producer credit summary for our liner notes
Retrieved 18 recording sessions between October and December. Producers involved: Alex Chen (9 sessions, primarily drums and bass tracking), Jordan Lee (5 sessions, vocal production), and Sam Patel (4 sessions, mixing). Most frequent studio: Eastside Sound (11 sessions). Based on session metadata, here's a draft credit block: 'Produced by Alex Chen, Jordan Lee, and Sam Patel. Recorded at Eastside Sound, Brooklyn. Engineering by [names from session records].' Note: 2 sessions are missing engineer credits.
This synthesis example shows the MCP feeding structured session data to the AI for creative output. The draft credit block is AI-generated from withPICA's session records, not a stored template. Accuracy depends on complete session metadata — gaps in producer or engineer fields will appear in the output.
Use-case deep-dives
When withPICA wins for quarterly royalty reconciliation
A 6-person indie label runs quarterly royalty checks across 200+ artists and 40 active agreements. The finance lead uses withPICA's List Agreements and List People tools to pull expiry states and linked catalog IDs into a shared Switchy workspace, then cross-references session credits against agreement templates. This works when your catalog is under 500 people and you need structured agreement data, not just PDFs in a folder. The API key auth means one seat can query the full org catalog without per-user permissioning overhead. If your label has multiple imprints or complex sub-publishing splits, you'll hit the tool's single-org scope and need manual reconciliation. For teams doing monthly royalty runs with clean agreement templates, withPICA keeps the audit in one workspace instead of toggling between spreadsheets and a web portal.
When withPICA handles pre-production talent checks
A 12-person production company preps a 3-week shoot with 30 crew and 8 on-camera talent. The line producer uses Get Person and List Sessions to verify each crew member's prior project credits and check agreement status before issuing contracts. This scenario wins when you're hiring repeat collaborators from a shared catalog and need to confirm their last engagement date or template tier. The workspace context tool surfaces org-wide health and priorities, so the PM can flag missing agreements in standup without opening withPICA's UI. If you're hiring mostly new talent or working across multiple production entities, the single-workspace scope limits cross-catalog lookups. For productions under 50 people with a stable crew pool, withPICA keeps onboarding checks in the same Switchy thread as scheduling and budget review.
When withPICA supports recurring guest booking
A 4-person podcast network books 8-12 guests per month across 3 shows. The booker uses List People and Get Person to pull guest bios, prior episode appearances, and agreement templates into a Switchy workspace shared with the host and editor. This works when your guest catalog is under 300 people and you need structured session history, not just email threads. The List Sessions tool shows which guests appeared on which episodes, so the team avoids repeat bookings too close together. If your network has multiple legal entities or you book mostly one-time guests, the catalog overhead outweighs the lookup speed. For networks with a recurring guest pool and standard agreement templates, withPICA keeps booking research in the same workspace as show notes and release scheduling.
Frequently asked
What does the withPICA MCP do in Switchy?
It connects your withPICA catalog to Switchy's AI workspace so your team can query people, projects, sessions, and agreements without leaving the conversation. You can search contributors, check contract expiry dates, pull session metadata, and verify who's linked to which projects — all through natural language prompts instead of clicking through the withPICA web app.
Do I need admin access to connect withPICA?
You need an API key from your withPICA organisation, which typically requires admin or owner permissions to generate. The MCP authenticates with that key and inherits the same access level as the user who created it. If your role can't view certain people or agreements in withPICA, the MCP won't surface them either.
Can the withPICA MCP create new agreements or edit people?
No. The MCP is read-only — it lists and retrieves catalog data but doesn't write anything back to withPICA. If you need to add a person, update a contract, or create a session, you still do that in the withPICA app. The MCP exists to surface existing records during team discussions, not to replace your catalog workflow.
How is this different from just opening withPICA in a browser tab?
The MCP lets your team ask questions like "who worked on Project X" or "which agreements expire this month" directly in Switchy, and the AI assembles the answer by querying withPICA in the background. You skip the manual search-filter-export loop. It's faster for ad-hoc lookups during planning or rights clearance conversations, but you still use the withPICA UI for bulk edits or visual catalog browsing.
Who on the team should connect the withPICA integration?
Whoever manages your withPICA account and can generate an API key — usually a catalog admin or production coordinator. Once connected, everyone in the Switchy workspace can query the catalog through prompts. The MCP doesn't count as a separate withPICA seat, but it does respect the permissions baked into the API key you provide.