@withpica/mcp-server 2.97.0 → 2.97.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +52 -0
- package/README.md +5 -1
- package/dist/lib/changelog.generated.d.ts +2 -2
- package/dist/lib/changelog.generated.d.ts.map +1 -1
- package/dist/lib/changelog.generated.js +2 -2
- package/dist/lib/changelog.generated.js.map +1 -1
- package/dist/server-instructions.d.ts +12 -2
- package/dist/server-instructions.d.ts.map +1 -1
- package/dist/server-instructions.js +13 -2
- package/dist/server-instructions.js.map +1 -1
- package/dist/tools/credits.js +1 -1
- package/dist/tools/credits.js.map +1 -1
- package/dist/tools/dashboard.d.ts.map +1 -1
- package/dist/tools/dashboard.js +24 -2
- package/dist/tools/dashboard.js.map +1 -1
- package/dist/tools/discovery.d.ts.map +1 -1
- package/dist/tools/discovery.js +12 -1
- package/dist/tools/discovery.js.map +1 -1
- package/dist/tools/duplicates.d.ts.map +1 -1
- package/dist/tools/duplicates.js +29 -3
- package/dist/tools/duplicates.js.map +1 -1
- package/dist/tools/index.d.ts.map +1 -1
- package/dist/tools/index.js +9 -2
- package/dist/tools/index.js.map +1 -1
- package/dist/tools/metadata.d.ts.map +1 -1
- package/dist/tools/metadata.js +31 -0
- package/dist/tools/metadata.js.map +1 -1
- package/dist/tools/recovery-hints.d.ts.map +1 -1
- package/dist/tools/recovery-hints.js +19 -0
- package/dist/tools/recovery-hints.js.map +1 -1
- package/dist/tools/releases.d.ts.map +1 -1
- package/dist/tools/releases.js +3 -1
- package/dist/tools/releases.js.map +1 -1
- package/dist/tools/selections.d.ts +42 -0
- package/dist/tools/selections.d.ts.map +1 -0
- package/dist/tools/selections.js +361 -0
- package/dist/tools/selections.js.map +1 -0
- package/dist/tools/subscription.d.ts.map +1 -1
- package/dist/tools/subscription.js +8 -2
- package/dist/tools/subscription.js.map +1 -1
- package/dist/tools/works.d.ts.map +1 -1
- package/dist/tools/works.js +1 -0
- package/dist/tools/works.js.map +1 -1
- package/package.json +16 -2
package/CHANGELOG.md
CHANGED
|
@@ -11,6 +11,58 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
11
11
|
|
|
12
12
|
## [Unreleased]
|
|
13
13
|
|
|
14
|
+
## [2.97.1] - 2026-09-08
|
|
15
|
+
|
|
16
|
+
### Added
|
|
17
|
+
|
|
18
|
+
- **`pica_catalog_health_fix` accepts `selections: [{actionId, chosenPersonId}]`**
|
|
19
|
+
— the human choice a `resolve_person` action needs (one of its
|
|
20
|
+
`preview.candidates[].personId`). A selection accepts its action; a choice
|
|
21
|
+
the plan never offered is skipped `guard_blocked` with the reason. Until now
|
|
22
|
+
the applier required a chosen person the tool had no way to pass, so every
|
|
23
|
+
accepted `resolve_person` came back `stale` (feedback 2026-09-05).
|
|
24
|
+
- **`pica_find_duplicates` sees identifier-less copies.** Recordings group on
|
|
25
|
+
title + artist and releases on title + equal track count when the ISRC/UPC
|
|
26
|
+
pass cannot see them (`match_kind: "title_artist"`, keep-separate default);
|
|
27
|
+
a UPC shared by releases with different titles is reported as
|
|
28
|
+
`shared_upc_different_title` — the decision is "correct the UPC", with no
|
|
29
|
+
fold option (feedback 2026-09-05).
|
|
30
|
+
|
|
31
|
+
### Fixed
|
|
32
|
+
|
|
33
|
+
- **`pica_works_update {collaborators}` is refused with a redirect** to
|
|
34
|
+
`pica_credits_update` / `pica_credit_add`. `works.collaborators` is a
|
|
35
|
+
legacy jsonb mirror; the write showed correct splits on inspect while the
|
|
36
|
+
`work_collaborators` rows every health check reads still disagreed, and the
|
|
37
|
+
health plan then proposed "fixing" them (feedback 2026-09-05).
|
|
38
|
+
- **Accepting a held finding is a typed 409, not `INTERNAL_ERROR`.** The
|
|
39
|
+
apply route now maps every "is already <status>" refusal to
|
|
40
|
+
`PROPOSAL_ALREADY_CLOSED`, and a held one carries the unlock sentence
|
|
41
|
+
(`pica_billing_pay`, offer `unlock`, `entity_id` the work) — a ChatGPT user
|
|
42
|
+
hit "internal server error" three times on 2026-09-04.
|
|
43
|
+
- **`pica_credit_add` never invents a share.** An omitted `share_pct` on a
|
|
44
|
+
composition credit is stored as NULL (unknown), not 0 — a 0 read as a real
|
|
45
|
+
share, so the health plan rescaled the other writer to 100 and the second
|
|
46
|
+
writer's stake vanished (holdout lock, 2026-09-06). For `credit_type:
|
|
47
|
+
"owner"` the share is now REQUIRED (`OWNER_SHARE_REQUIRED`, 422): master
|
|
48
|
+
ownership is recorded as given, never assumed to be 100.
|
|
49
|
+
- **`pica_releases_update` documents the UPC backfill trigger** — it fires
|
|
50
|
+
only on a write to `spotify_album_id`, so re-sending the existing id is the
|
|
51
|
+
way to backfill a UPC (ops issue 9f33cc59).
|
|
52
|
+
|
|
53
|
+
- **`pica_subscription_status` is callable on the hosted connector.** It was
|
|
54
|
+
declared `scope: admin`, `audiences: ["stdio"]` while `pica_billing_pay` was
|
|
55
|
+
`read:catalog` on both surfaces, so a connected agent could mint a pay link
|
|
56
|
+
but not read the plan it would be paying for (`callable_on_this_surface:
|
|
57
|
+
false` on claude.ai, 2026-09-04). Both now share the catalogue-read floor;
|
|
58
|
+
`pica_subscription_manage` stays stdio + admin.
|
|
59
|
+
- **The pay path is visible to an agent that never calls `pica_discover`.**
|
|
60
|
+
The server instructions name `pica_subscription_status` and
|
|
61
|
+
`pica_billing_pay` with the exact `pica_execute` shape inside the first
|
|
62
|
+
2,000 characters (the observed cut on the claude.ai connector), and the
|
|
63
|
+
`pica_discover` description lists "how do i pay pica" among its example
|
|
64
|
+
queries for clients that surface tool descriptions but not instructions.
|
|
65
|
+
|
|
14
66
|
PR #2118 (`fix/avatar-import-path-2026-09-03`) is merged into the release branch, so its changes ship in the version below; publish in the order mcp-utils → mcp-sdk → mcp-server.
|
|
15
67
|
|
|
16
68
|
## [2.97.0] - 2026-09-04
|
package/README.md
CHANGED
|
@@ -65,7 +65,7 @@ Read tools are annotated read-only and are safe to call freely. Write tools repo
|
|
|
65
65
|
|
|
66
66
|
## Tools
|
|
67
67
|
|
|
68
|
-
|
|
68
|
+
335 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.
|
|
69
69
|
|
|
70
70
|
**works** — manage your musical works
|
|
71
71
|
|
|
@@ -235,6 +235,10 @@ Read tools are annotated read-only and are safe to call freely. Write tools repo
|
|
|
235
235
|
|
|
236
236
|
`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`
|
|
237
237
|
|
|
238
|
+
**selections** — save, recall, and resolve named catalog selections — persisted predicates over the catalogue with an honest coverage report
|
|
239
|
+
|
|
240
|
+
`pica_selections_create`, `pica_selections_query`, `pica_selections_inspect`, `pica_selections_update`, `pica_selections_delete`
|
|
241
|
+
|
|
238
242
|
**share links** — create, inspect, update, and delete share links for catalog content
|
|
239
243
|
|
|
240
244
|
`pica_share_links_create`, `pica_share_links_query`, `pica_share_links_inspect`, `pica_share_links_update`, `pica_share_links_delete`
|