@withpica/mcp-server 2.56.0 → 2.56.1

package/CHANGELOG.md

@@ -11,6 +11,39 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.56.1] - 2026-05-17
+
+### Changed
+
+- Brand consistency: "PICA" → "withPICA" in package metadata, keywords (added `"withpica"`, `"music-catalog"`, `"music-rights"`), README, JSDoc headers, and customer-visible tool descriptions: `pica_delete_my_account`, `pica_gdpr_export_my_data` (description + completion message), `pica_telegram_connect`, `pica_onboarding_complete` (description + `intent_notes` field), and the `new-catalog-setup` prompt.
+- Registered `pica_works_attest` and `pica_credits_send_for_attestation` in `REQUIRED_SCHEMAS_SOURCE` companion_calls (both tools declared workflow membership but weren't referenced — pre-existing drift caught by `lint:required-schemas`).
+
+### Fixed
+
+- **`pica_submit_feedback` + `pica_physical_assets_create` no longer leak SDK errors to the user (PRs #453 + #457, 2026-05-15).**
+  Both executors had naked SDK calls — when the upstream API errored, the
+  framework's outer catch in `tools/index.ts` JSON-stringified the error
+  body straight to the conversation (`{error: "UNKNOWN_ERROR", message: "..."}`).
+  Wrap each SDK call in `try/catch`: on throw, fire-and-forget
+  `pica.opsIssues.reportIssue({ kind: "tool_failure", ... })` with the
+  underlying message + status + parameter shape in `context`, return
+  neutral text (`"couldn't <verb> right now — the team has been alerted."`).
+  Input-validation early-returns are preserved — those carry actionable
+  text and aren't server failures. PR #457 added `tool_failure` to the
+  `OpsIssueExplicitKind` taxonomy and retagged both wrappers (PR #453
+  shipped as `kind: "data_issue"` because `tool_failure` didn't exist
+  yet). 12 new unit tests across `feedback.test.ts` (new file) +
+  `assets.test.ts`. **Note:** the auto-audit upsert path is bypassed
+  because returning `isError: true` logs as `result_status: "success"`
+  (`tools/index.ts:1859`) — the executor reports manually instead.
+
+### Added
+
+- **`pica_report_issue` accepts `kind: "tool_failure"` (PR #457, 2026-05-15).**
+  Sixth value in the agent-explicit kinds enum. Lets agents file SDK /
+  upstream-tool failures directly via the report-issue tool, mirroring
+  the new fail-quiet wrappers.
+
 ## [2.56.0] - 2026-05-14
 
 ### Added

package/README.md

@@ -1,10 +1,10 @@
-# PICA MCP Server
+# withPICA MCP Server
 
-Model Context Protocol (MCP) server for the PICA Platform. Enables **any MCP-compatible AI assistant** to interact with your PICA music catalog.
+Model Context Protocol (MCP) server for withPICA. Enables **any MCP-compatible AI assistant** to interact with your withPICA music catalog.
 
 ## What is MCP?
 
-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 PICA catalog.
+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.
 
 ## Compatible AI Assistants
 
@@ -89,9 +89,9 @@ npm link
 
 ## Configuration
 
-### Get Your PICA API Key
+### Get Your withPICA API Key
 
-1. Log into PICA at https://withpica.com
+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
@@ -123,7 +123,7 @@ The setup process is similar for any MCP-compatible tool:
 
 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 PICA tools and resources
+3. The AI can now access all withPICA tools and resources
 
 ## Usage Examples
 
@@ -267,7 +267,7 @@ Make sure you've set the API key in your MCP server configuration:
 ## Architecture
 
 ```
-MCP Server for PICA
+MCP Server for withPICA
 ├── Protocol Handler (MCP standard)
 ├── Authentication (API key)
 ├── Tools (24 AI-callable functions)
@@ -281,7 +281,7 @@ MCP Server for PICA
 
 ## Security
 
-- All requests require a valid PICA API key
+- 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
@@ -301,4 +301,4 @@ MIT
 Built with:
 
 - [@modelcontextprotocol/sdk](https://github.com/modelcontextprotocol/sdk) - MCP SDK
-- [@withpica/sdk](https://www.npmjs.com/package/@withpica/sdk) - PICA TypeScript SDK
+- [@withpica/sdk](https://www.npmjs.com/package/@withpica/sdk) - withPICA TypeScript SDK