@withpica/mcp-server 2.95.3 → 2.96.0

package/README.md

@@ -1,304 +1,288 @@
-# withPICA MCP Server
+<!-- GENERATED FILE — do not edit by hand.
+     Prose lives in mcp-server/README.intro.md; the tool inventory is
+     derived from the source registries. Regenerate with
+     `node scripts/build-mcp-readmes.mjs`; `--check` fails on drift. -->
 
-Model Context Protocol (MCP) server for withPICA. Enables **any MCP-compatible AI assistant** to interact with your withPICA music catalog.
+# @withpica/mcp-server
 
-## What is MCP?
+MCP server for **withPICA** — music catalog management through conversation. Works, recordings, credits, agreements, rights, royalties, enrichment and registration-ready exports, from Claude, ChatGPT, Cursor, or any MCP-compatible client.
 
-The Model Context Protocol (MCP) is an open standard that enables AI assistants to securely access external data and functionality. With this MCP server, any MCP-compatible AI can interact with your withPICA catalog.
+> **Not the same product as `@picahq/mcp`.** That is Pica / picaos.com, an unrelated API-integrations tool that happens to share the short name. If your assistant starts talking about integrations it never set up, or asks you to paste credentials into a dashboard, you have the other one installed.
 
-## Compatible AI Assistants
+## Install
 
-- **Claude Desktop** - Anthropic's desktop AI assistant
-- **ChatGPT** - OpenAI's assistant (when MCP support is available)
-- **Custom AI tools** - Any application that implements the MCP protocol
-- **Future AI assistants** - As more tools adopt MCP
+```bash
+claude mcp add withpica -- npx --yes @withpica/mcp-server@latest
+```
 
-## Features
+Or, in any client that reads an `mcpServers` config:
 
-### 24 AI-Callable Tools
+```json
+{
+  "mcpServers": {
+    "withpica": {
+      "command": "npx",
+      "args": ["@withpica/mcp-server"]
+    }
+  }
+}
+```
 
-**Works Management (8 tools)**
+## Signing in
 
-- `pica_works_list` - List musical works
-- `pica_works_get` - Get work details
-- `pica_works_create` - Create new work
-- `pica_works_update` - Update work
-- `pica_works_delete` - Delete work
-- `pica_works_verify` - Verify work
-- `pica_works_search` - Search works
-- `pica_works_bulk_delete` - Delete multiple works
+**On stdio (this package), no API key is needed up front.** Say _"sign me in to withpica"_ in chat; `pica_sign_in` emails you a magic link, you click it, and your tools unlock. `PICA_API_KEY` in the environment also works and skips the link.
 
-**People Management (8 tools)**
+**On the hosted HTTP transport** (`https://withpica.com/api/mcp`) there is no in-chat sign-in — `pica_sign_in` and `pica_sign_out` are stdio-only, because the credential file they write would land on an ephemeral filesystem your client never reads. Connect over OAuth 2.1 instead (dynamic client registration + PKCE S256, discovery at `https://withpica.com/.well-known/oauth-protected-resource`), or send an API key as a Bearer token. A Bearer caller should call `pica_introduce_self` first: PICA stamps that declaration onto every audit row that follows, so the owner can later reconstruct what their agent did.
 
-- `pica_people_list` - List people
-- `pica_people_get` - Get person details
-- `pica_people_create` - Create new person
-- `pica_people_update` - Update person
-- `pica_people_delete` - Delete person
-- `pica_people_search` - Search people
-- `pica_people_enrich_isni` - Enrich from ISNI
-- `pica_people_enrich_musicbrainz` - Enrich from MusicBrainz
+API keys are created and revoked at <https://withpica.com/settings?tab=connections>.
 
-**Recordings Management (5 tools)**
+## How the tools are surfaced
 
-- `pica_recordings_query` - List/search recordings; filter by `work_id` (replaces removed `pica_recordings_by_work`)
-- `pica_recordings_inspect` - Get recording details (sections-based)
-- `pica_recordings_create` - Create new recording
-- `pica_recordings_update` - Update recording
-- `pica_recordings_delete` - Delete recording
+Over HTTP the server advertises a small meta-tool surface by default — `pica_discover` → `pica_tool_details` → `pica_execute` — so a schema-constrained client is not handed the whole registry at once. Every tool stays callable by name. Add `?layered=0` to the endpoint for the eager list.
 
-**Search & Analytics (2 tools)**
+Over stdio the full set is listed directly.
 
-- `pica_search_all` - Search across all entities
-- `pica_catalog_stats` - Get catalog statistics
+`pica_skill_list` / `pica_skill_get` load methodologies (catalog-audit, register-my-works, prepare-for-sync) as needed, rather than at handshake.
 
-### 4 Data Resources
+## Safety
 
-Read-only access to catalog data:
+Read tools are annotated read-only and are safe to call freely. Write tools report what changed. Destructive tools (delete, merge) require a two-step confirmation token and an elevated scope that ordinary agent grants cannot hold.
 
-- `works://list` - All works
-- `people://list` - All people
-- `recordings://list` - All recordings
-- `catalog://stats` - Catalog statistics
+## Environment variables
 
-### 4 Workflow Prompts
+| variable       | required | meaning                                           |
+| -------------- | -------- | ------------------------------------------------- |
+| `PICA_API_KEY` | no       | skips the magic-link flow                         |
+| `PICA_API_URL` | no       | API base URL (default `https://withpica.com/api`) |
+| `DEBUG`        | no       | verbose logging to stderr (`true` / `1`)          |
 
-Pre-configured prompts for common tasks:
+## Links
 
-- `analyze-catalog` - Comprehensive catalog analysis
-- `find-duplicates` - Find duplicate entries
-- `enrich-metadata` - Identify enrichment opportunities
-- `verify-works` - Review unverified works
+- Connect guide: <https://withpica.com/connect>
+- Machine-readable: <https://withpica.com/llms.txt>, <https://withpica.com/connect/llms.txt>
+- Discovery: <https://withpica.com/.well-known/mcp.json>
+- Support: support@withpica.com
 
-## Installation
+## Tools
 
-### NPM (Recommended)
+329 tools, grouped below by the taxonomy `pica_discover` uses. The server's own `tools/list` is authoritative — not every registered tool is filed under a category yet, so the names below are a map, not a census.
 
-```bash
-npm install -g @withpica/mcp-server
-```
+**works** — manage your musical works
 
-### From Source
+`pica_works_query`, `pica_works_inspect`, `pica_works_create`, `pica_register_set`, `pica_works_update`, `pica_works_delete`, `pica_works_bulk_delete`, `pica_works_bulk_update`, `pica_works_bulk_link_artist`, `pica_works_bulk_add_collaborator`, `pica_work_writers_add`, `pica_works_bulk_copy_credits`, `pica_works_bulk_move_to_performances`, `pica_works_verify`, `pica_works_verify_registrations`, `pica_works_attest`, `pica_catalog_diligence`
 
-```bash
-cd mcp-server
-npm install
-npm run build
-npm link
-```
+**people** — manage people in your catalog
 
-## Configuration
+`pica_people_query`, `pica_people_inspect`, `pica_people_create`, `pica_people_update`, `pica_people_delete`, `pica_people_bulk_delete`, `pica_people_bulk_update_roles`, `pica_people_bulk_add_tags`, `pica_group_add_member`, `pica_group_remove_member`, `pica_group_list_members`, `pica_person_list_groups`, `pica_artist_projects`
 
-### Get Your withPICA API Key
+**groups** — manage group → member relationships on people
 
-1. Log into withPICA at https://withpica.com
-2. Go to Settings → API Keys
-3. Generate a new API key
-4. Copy the key for use below
+`pica_group_add_member`, `pica_group_remove_member`, `pica_group_list_members`, `pica_person_list_groups`
 
-### Claude Desktop Setup
+**recordings** — manage recordings linked to works
 
-Add to your Claude Desktop configuration file:
+`pica_recordings_query`, `pica_recordings_inspect`, `pica_recordings_create`, `pica_recordings_update`, `pica_recordings_delete`, `pica_recordings_bulk_reassign_artist`
 
-**macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
-**Windows**: `%APPDATA%\Claude\claude_desktop_config.json`
+**credits** — manage work credits, contributors, and first-party recording-side production credits
 
-```json
-{
-  "mcpServers": {
-    "pica": {
-      "command": "npx",
-      "args": ["-y", "@withpica/mcp-server"],
-      "env": {
-        "PICA_API_KEY": "your-api-key-here"
-      }
-    }
-  }
-}
-```
+`pica_credits_list`, `pica_credits_update`
 
-### Other MCP-Compatible AI Assistants
+**sharing** — explain why a user or org can see a work, recording, or person — surfaces the chain of reasons (org membership, custody chain, share links, cross-org grants); send works to named recipients via withPICA-branded email
 
-The setup process is similar for any MCP-compatible tool:
+`pica_share_trace`, `pica_share_send`
 
-1. Configure the MCP server command: `npx -y @withpica/mcp-server`
-2. Set the `PICA_API_KEY` environment variable
-3. The AI can now access all withPICA tools and resources
+**explainability** — explain dashboard / briefing count discrepancies — when a number doesn't match what the user sees elsewhere
 
-## Usage Examples
+`pica_count_explain`
 
-### Example 1: List Your Works
+**multimedia** — manage photos, videos, and media linked to works
 
-**User**: "Show me my musical works"
+`pica_multimedia_search`, `pica_multimedia_create`, `pica_multimedia_import_url`, `pica_multimedia_link_youtube`, `pica_multimedia_link_work`, `pica_upload`
 
-**AI** uses: `pica_works_list`
+**audio** — manage and analyze audio files
 
-**Result**: List of works with titles, ISWCs, verification status, etc.
+`pica_audio_query`, `pica_audio_inspect`, `pica_audio_presigned_upload`, `pica_audio_complete_upload`, `pica_audio_analyze`, `pica_audio_identify`, `pica_audio_assign`, `pica_audio_bulk_assign_suggested`, `pica_audio_dismiss_match`, `pica_audio_update`, `pica_audio_delete`, `pica_upload`, `pica_audio_pipeline_status`
 
-### Example 2: Create a Work
+**projects** — manage albums, EPs, and work groupings
 
-**User**: "Create a new composition called 'Moonlight Sonata No. 2'"
+`pica_projects_query`, `pica_projects_inspect`, `pica_projects_create`, `pica_projects_update`, `pica_projects_delete`, `pica_projects_attach_works`, `pica_projects_participants`, `pica_projects_multimedia`
 
-**AI** uses: `pica_works_create` with appropriate parameters
+**releases** — manage releases with dates, labels, and UPCs
 
-**Result**: New work created with generated ID
+`pica_releases_query`, `pica_releases_inspect`, `pica_releases_create`, `pica_releases_update`, `pica_releases_delete`, `pica_releases_move_track`, `pica_releases_create_with_tracks`, `pica_releases_completeness_check`, `pica_releases_attach_track`, `pica_releases_attach_recording_with_work`, `pica_releases_detach_track`, `pica_releases_list_tracks`, `pica_releases_reorder_tracks`, `pica_release_show`
 
-### Example 3: Analyze Catalog
+**sessions** — track work sessions and studio time
 
-**User**: "Analyze my catalog"
+`pica_sessions_query`, `pica_sessions_inspect`, `pica_sessions_create`, `pica_sessions_types`
 
-**AI** uses: `analyze-catalog` prompt
+**notes** — create and manage catalog notes
 
-**AI calls**:
+`pica_notes_query`, `pica_notes_inspect`, `pica_notes_create`, `pica_notes_delete`
 
-- `pica_catalog_stats` - Get statistics
-- `pica_works_list` - Review works
-- `pica_people_list` - Review people
+**duplicates** — detect and merge duplicate records
 
-**Result**: Comprehensive analysis with insights and recommendations
+`pica_find_duplicates`, `pica_merge_duplicates`
 
-### Example 4: Find Duplicates
+**import** — import catalog data from files and streaming services
 
-**User**: "Find duplicate entries"
+`pica_import_fields`, `pica_import_template`, `pica_import_analyze`, `pica_import_validate`, `pica_import_execute`, `pica_import_streaming_link`, `pica_import_documents_query`, `pica_import_documents_inspect`, `pica_import_youtube_link`, `pica_ingest_statement`
 
-**AI** uses: `find-duplicates` prompt
+**export** — export catalog data in various formats
 
-**AI calls**:
+`pica_export_catalog_csv`, `pica_export_song_registration`, `pica_export_industry_ready`, `pica_export_catalog_asset_report`, `pica_export_ai_consent`, `pica_export_snapshot`, `pica_export_ownership_record`, `pica_export_rights_proof`, `pica_export_diligence_pack`, `pica_download`, `pica_export_my_data`
 
-- `pica_works_list` - Get all works
-- `pica_people_list` - Get all people
+**search** — search across the catalog and discover content
 
-**Result**: List of potential duplicates with merge recommendations
+`pica_search_all`, `pica_catalog_stats`, `pica_graph_traverse`, `pica_discoveries_query`, `pica_discoveries_review`, `pica_claim_credit`, `pica_claim_custody`, `pica_claim_artist`
 
-### Example 5: Enrich Metadata
+**analytics** — provenance, carbon, and catalog analytics
 
-**User**: "Enrich Mozart's profile from ISNI"
+`pica_provenance_stats`, `pica_provenance_work`, `pica_provenance_certificate`, `pica_provenance_certificate_get`, `pica_carbon_footprint`, `pica_carbon_live`, `pica_catalog_diligence`, `pica_run_person_cascade`, `pica_run_work_cascade`, `pica_cascade_health`, `pica_car_preview`, `pica_audit_list`
 
-**AI** uses: `pica_people_enrich_isni` with person ID and ISNI
+**documents** — analyse documents with ai
 
-**Result**: Person record updated with enriched data from ISNI
+`pica_documents_analyse`, `pica_documents_query`, `pica_documents_inspect`, `pica_documents_link`, `pica_documents_delete`, `pica_upload`
 
-## Use Cases
+**calendar** — view catalog calendar events
 
-### For Catalog Managers
+`pica_calendar_events`
 
-- "Show me all unverified works"
-- "Find duplicate entries"
-- "List works missing ISWC codes"
-- "Enrich all people from ISNI"
+**publishers** — look up and create publishers
 
-### For Data Analysis
+`pica_publishers_query`, `pica_publishers_create`
 
-- "What's the average duration of my compositions?"
-- "Who are my most prolific composers?"
-- "Which works have the most recordings?"
-- "Show me catalog statistics"
+**briefing** — get your daily catalog briefing and dashboard
 
-### For Enrichment
+`pica_dashboard_attention`, `pica_dashboard_briefing`, `pica_catalog_health`, `pica_catalog_health_plan`, `pica_catalog_health_fix`, `pica_integrity_waive`
 
-- "Find all people that could be enriched from MusicBrainz"
-- "Suggest ISNI matches for unverified artists"
-- "Which works are missing metadata?"
+**enrichment** — enrich your catalog metadata from external sources
 
-### For Bulk Operations
+`pica_resolve_work`, `pica_resolve_person`, `pica_resolve_recording`, `pica_resolve_release`, `pica_people_triangulate`, `pica_enrichment_candidates`, `pica_enrichment_compare`, `pica_registrations_compare`, `pica_enrichment_propose`, `pica_enrichment_proposal_apply`, `pica_enrichment_proposal_reject`, `pica_enrichment_proposals_list`, `pica_enrichment_proposals_bulk_reject`, `pica_enrichment_proposals_bulk_apply`, `pica_enrichment_clear`
 
-- "Create works from this list"
-- "Verify all completed works"
-- "Delete test entries"
+**feedback** — report problems and submit feedback to the PICA team — call proactively when you hit a workflow gap or the user says 'this is broken'
 
-## Environment Variables
+`pica_report_issue`, `pica_my_reported_issues`, `pica_submit_feedback`
 
-- `PICA_API_KEY` (required) - Your PICA API key
-- `PICA_API_URL` (optional) - API base URL (default: https://withpica.com/api)
-- `DEBUG` (optional) - Enable debug logging (set to 'true' or '1')
+**onboarding** — acknowledge MCP onboarding for OAuth-arrived users — call after walking the user through identity, security, and intent
 
-## Development
+`pica_acknowledge_onboarding`
 
-### Build
+**agent hygiene** — declare who you are, log workflow milestones, read what's been getting done, and check whether a deferred write has been approved — agent observability
 
-```bash
-npm run build
-```
+`pica_introduce_self`, `pica_outcome_log`, `pica_outcomes_recent`, `pica_approval_status`
 
-### Development Mode
+**signup** — create a new withPICA account from inside the agent — for users without a connection key. existing users use pica_sign_in instead.
 
-```bash
-npm run dev
-```
+`pica_signup_start`
 
-### Local Testing
+**memory** — save and recall workspace memories across sessions; review your recent assistant activity
 
-```bash
-PICA_API_KEY=your-key npm run dev
-```
+`pica_memory_list`, `pica_memory_search`, `pica_memory_save`, `pica_memory_delete`, `pica_memory_update`, `pica_my_recent_questions`
 
-## Troubleshooting
+**skills** — discover and load PICA's named methodologies (catalog-audit, register-my-works, prepare-for-sync, etc.) — triggered by phrases like 'audit my catalog'
 
-### "PICA_API_KEY environment variable is required"
+`pica_skill_list`, `pica_skill_get`
 
-Make sure you've set the API key in your MCP server configuration:
+**platform** — platform release notes for the PICA MCP server — what's new, what changed, version history. NOT for catalog activity (use briefing / works / recordings for that)
 
-```json
-{
-  "env": {
-    "PICA_API_KEY": "your-actual-api-key"
-  }
-}
-```
+`pica_release_notes`
 
-### "Authentication failed"
+**account** — check storage and integrations; connect your own cloud storage (BYOC) or revert to PICA-managed
 
-- Verify your API key is correct
-- Check that the API key hasn't been revoked
-- Generate a new API key if needed
+`pica_storage_status`, `pica_storage_configure_start`, `pica_storage_disconnect`, `pica_delete_my_account`
 
-### Tools Not Showing Up
+**subscription** — what does pica cost, how do I pay, and what is pica holding — read your billing state and get a pay link
 
-1. Restart your AI assistant after configuring the MCP server
-2. Check the MCP server logs for errors
-3. Verify the configuration file syntax is correct
+`pica_subscription_status`, `pica_billing_pay`, `pica_subscription_manage`
 
-### Connection Issues
+**profile** — manage your user, organisation, and directory profile
 
-- Ensure you have an internet connection
-- Check that https://withpica.com is accessible
-- Verify no firewall is blocking the connection
+`pica_user_profile`, `pica_organisation_profile`, `pica_directory_settings`, `pica_update_my_identity`, `pica_update_organisation_profile`, `pica_users_get_my_profile`, `pica_users_set_handle`, `pica_users_clear_handle`, `pica_users_set_bio`, `pica_users_set_avatar_url`, `pica_users_import_bio_from_person`, `pica_users_find_by_handle`
 
-## Architecture
+**privacy** — self-service privacy & account controls — read/update marketing opt-ins, request GDPR data export, delete your account
 
-```
-MCP Server for withPICA
-├── Protocol Handler (MCP standard)
-├── Authentication (API key)
-├── Tools (24 AI-callable functions)
-│   ├── Works Management (8)
-│   ├── People Management (8)
-│   ├── Recordings Management (6)
-│   └── Search & Analytics (2)
-├── Resources (4 data providers)
-└── Prompts (4 workflows)
-```
+`pica_get_privacy_settings`, `pica_update_privacy_settings`, `pica_export_my_data`, `pica_delete_my_account`, `pica_export_ai_consent`
+
+**uploads** — upload files to the platform and share them out via secure delivery links
+
+`pica_upload`, `pica_upload_file`, `pica_upload_complete`, `pica_file_deliver`, `pica_file_revoke_delivery`
+
+**agreements** — manage agreements, agreement templates, and agreement types
+
+`pica_agreements_query`, `pica_agreements_inspect`, `pica_agreements_create`, `pica_agreements_create_from_template`, `pica_agreements_update`, `pica_agreements_delete`, `pica_agreements_link_work`, `pica_agreements_send_for_signature`, `pica_agreement_source_splits`, `pica_agreement_templates_duplicate`, `pica_agreement_templates_render`, `pica_agreement_templates_set_default`, `pica_agreement_types_query`, `pica_agreement_types_inspect`, `pica_agreement_types_create`, `pica_agreement_types_update`, `pica_agreement_types_delete`
+
+**collaborators** — invite, accept, dispute, and claim-by-code catalog collaborators
+
+`pica_collaborators_invite`, `pica_collaborators_invite_bulk`, `pica_collaborators_invite_resend`, `pica_collaborators_invites_list`, `pica_collaborators_incoming_list`, `pica_collaborators_accept`, `pica_collaborators_dispute`, `pica_disputes_list`, `pica_collaborators_claim_by_code`, `pica_collaborators_decline_by_code`, `pica_collaborators_invite_status`, `pica_collaborators_invite_revoke`, `pica_collaborations_received`, `pica_collaborators_counter_propose`, `pica_collaborators_accept_counter`, `pica_collaborators_decline_counter`, `pica_collaborators_counter_back`
+
+**consent** — read what the catalogue is cleared for under AI/usage consent, and who is blocking
+
+`pica_consent_readiness`, `pica_export_ai_consent`
+
+**custody** — manage catalog custody claims and reconciliation
+
+`pica_custody_list`, `pica_custody_history`, `pica_custody_claim`, `pica_custody_respond`, `pica_custody_reconcile`, `pica_custody_resolve_pending`, `pica_recording_custody_assign`, `pica_recording_provenance`, `pica_recording_samples_list`, `pica_recording_samples_add`, `pica_recording_samples_set_status`, `pica_recording_samples_remove`, `pica_claim_custody`
+
+**physical assets** — manage physical assets (master tapes, hardware, artefacts)
+
+`pica_physical_assets_query`, `pica_physical_assets_inspect`, `pica_physical_assets_create`, `pica_physical_assets_update`, `pica_physical_assets_delete`, `pica_physical_assets_export`, `pica_physical_assets_stats`, `pica_physical_assets_link_work`, `pica_physical_assets_link_recording`, `pica_physical_assets_unlink_work`, `pica_physical_assets_unlink_recording`
+
+**recording splits** — manage recording (master) splits between contributors
+
+`pica_recording_splits_list`, `pica_recording_splits_create`, `pica_recording_splits_verify`, `pica_split_sheet_generate`, `pica_recording_credits_update`
+
+**royalties statements** — view royalties and ingested statements
+
+`pica_royalties_summary`, `pica_royalties_list`, `pica_royalties_get`, `pica_statements_query`, `pica_statements_inspect`, `pica_ingest_statement`, `pica_statements_pending`, `pica_statement_ingest_document`, `pica_royalties_unmatched`, `pica_royalties_attribute`
+
+**share links** — create, inspect, update, and delete share links for catalog content
+
+`pica_share_links_create`, `pica_share_links_query`, `pica_share_links_inspect`, `pica_share_links_update`, `pica_share_links_delete`
+
+**access simulation** — simulate who would see what before mutating — share-link previews and access decisions
+
+`pica_access_simulate`
+
+**split sheets** — generate, send, and look up split sheets
+
+`pica_split_sheet_generate`, `pica_split_sheet_send`, `pica_split_sheet_get`, `pica_split_sheet_list`
+
+**licensing** — submit, list, and respond to license enquiries; search for sync
+
+`pica_submit_license_enquiry`, `pica_get_license_enquiry`, `pica_list_license_enquiries`, `pica_update_license_enquiry_status`, `pica_search_for_sync`
+
+**bookings** — search, list, and respond to internal-team booking enquiries (session/production requests)
+
+`pica_bookings_query`, `pica_bookings_update`
+
+**sync placements** — manage sync placements (films/TV/ads/games licensing your works) — placement records, evidence, verification state
+
+`pica_sync_placements_query`, `pica_sync_placements_inspect`, `pica_sync_placements_create`, `pica_sync_placements_update`, `pica_sync_placements_delete`, `pica_sync_placements_cite`
+
+**notifications** — list and schedule notifications to users and people
+
+`pica_notifications_list`, `pica_notifications_mark_read`, `pica_notify_user`, `pica_notify_user_at`, `pica_notify_user_cancel`, `pica_notify_user_list_pending`, `pica_notify_person`, `pica_notifications_recent`, `pica_notification_acknowledge`
+
+**messaging** — send and resend messages to collaborators and contacts
+
+`pica_send_message`, `pica_send_resend`, `pica_send_query`, `pica_send_cancel`
+
+**agent identity** — manage AI agent identities, grants, and activity
 
-## Security
+`pica_create_agent_identity`, `pica_issue_agent_grant`, `pica_revoke_agent_grant`, `pica_list_my_agent_grants`, `pica_get_agent_activity`
 
-- All requests require a valid withPICA API key
-- API keys are transmitted securely over HTTPS
-- Data access is scoped to your organization
-- No data is stored by the MCP server
+**telegram** — connect and inspect Telegram channel for the workspace
 
-## Support
+`pica_telegram_connect`, `pica_telegram_status`, `pica_telegram_config`
 
-- **Documentation**: https://docs.withpica.com
-- **Issues**: https://github.com/withpica/pica/issues
-- **Email**: support@withpica.com
+**labels** — look up and create record labels / distributors, and invite them to claim their organisation
 
-## License
+`pica_labels_query`, `pica_labels_create`, `pica_party_claim_invite`, `pica_party_claim_status`
 
-MIT
+**shows** — log live shows and tour credits, and confirm setlist matches against your catalogue
 
-## Credits
+`pica_log_show`, `pica_shows_query`, `pica_setlist_match`
 
-Built with:
+---
 
-- [@modelcontextprotocol/sdk](https://github.com/modelcontextprotocol/sdk) - MCP SDK
-- [@withpica/sdk](https://www.npmjs.com/package/@withpica/sdk) - withPICA TypeScript SDK
+Generated for `@withpica/mcp-server@2.95.4`. © 2024-2026 Withpica Ltd. All rights reserved. MIT licensed.