@withpica/mcp-server 2.4.0 → 2.4.2

package/dist/tools/works.d.ts

@@ -4,50 +4,50 @@
 import { PicaClient } from "../pica-sdk.js";
 import { ToolDefinition, ToolExecutor } from "./index.js";
 export declare class WorksTools {
-    private pica;
-    constructor(pica: PicaClient);
-    /**
-     * Get all works tools
-     */
-    getTools(): Array<{
-        definition: ToolDefinition;
-        executor: ToolExecutor;
-    }>;
-    /**
-     * List works (server-side search and pagination)
-     */
-    private listWorks;
-    /**
-     * Get work by ID
-     */
-    private getWork;
-    /**
-     * Create work
-     */
-    private createWork;
-    /**
-     * Update work
-     */
-    private updateWork;
-    /**
-     * Delete work
-     */
-    private deleteWork;
-    /**
-     * Verify work
-     */
-    private verifyWork;
-    /**
-     * Search works (server-side)
-     */
-    private searchWorks;
-    /**
-     * Bulk delete works
-     */
-    private bulkDeleteWorks;
-    /**
-     * Get full work context bundle
-     */
-    private getWorkFull;
+  private pica;
+  constructor(pica: PicaClient);
+  /**
+   * Get all works tools
+   */
+  getTools(): Array<{
+    definition: ToolDefinition;
+    executor: ToolExecutor;
+  }>;
+  /**
+   * List works (server-side search and pagination)
+   */
+  private listWorks;
+  /**
+   * Get work by ID
+   */
+  private getWork;
+  /**
+   * Create work
+   */
+  private createWork;
+  /**
+   * Update work
+   */
+  private updateWork;
+  /**
+   * Delete work
+   */
+  private deleteWork;
+  /**
+   * Verify work
+   */
+  private verifyWork;
+  /**
+   * Search works (server-side)
+   */
+  private searchWorks;
+  /**
+   * Bulk delete works
+   */
+  private bulkDeleteWorks;
+  /**
+   * Get full work context bundle
+   */
+  private getWorkFull;
 }
-//# sourceMappingURL=works.d.ts.map
+//# sourceMappingURL=works.d.ts.map

package/dist/utils/errors.d.ts

@@ -2,28 +2,28 @@
  * Error handling utilities for MCP server
  */
 export declare class McpServerError extends Error {
-    code: string;
-    details?: any | undefined;
-    constructor(message: string, code: string, details?: any | undefined);
+  code: string;
+  details?: any | undefined;
+  constructor(message: string, code: string, details?: any | undefined);
 }
 export declare class AuthenticationError extends McpServerError {
-    constructor(message?: string, details?: any);
+  constructor(message?: string, details?: any);
 }
 export declare class ToolExecutionError extends McpServerError {
-    constructor(message: string, details?: any);
+  constructor(message: string, details?: any);
 }
 export declare class ResourceError extends McpServerError {
-    constructor(message: string, details?: any);
+  constructor(message: string, details?: any);
 }
 /**
  * Format error for MCP response
  */
 export declare function formatError(error: any): {
-    type: string;
-    text: string;
+  type: string;
+  text: string;
 };
 /**
  * Log error with structured context (JSON to stderr for machine parsing)
  */
 export declare function logError(context: string, error: any): void;
-//# sourceMappingURL=errors.d.ts.map
+//# sourceMappingURL=errors.d.ts.map

package/dist/utils/formatting.d.ts

@@ -5,11 +5,11 @@
  * AND a structuredContent object for machine parsing (ADR-104 §1.2).
  */
 export interface FormattedResult {
-    content: Array<{
-        type: string;
-        text: string;
-    }>;
-    structuredContent?: Record<string, unknown>;
+  content: Array<{
+    type: string;
+    text: string;
+  }>;
+  structuredContent?: Record<string, unknown>;
 }
 /**
  * Format data as JSON text for MCP response
@@ -20,10 +20,10 @@ export declare function formatAsText(data: any): FormattedResult;
  * The LLM decides whether and how to surface these to the user.
  */
 export interface CompletionHint {
-    gap: string;
-    suggestion: string;
-    count?: number;
-    severity?: "critical" | "important" | "nice_to_have";
+  gap: string;
+  suggestion: string;
+  count?: number;
+  severity?: "critical" | "important" | "nice_to_have";
 }
 /**
  * Format success message, with optional completion hints for the guided loop.
@@ -32,16 +32,26 @@ export interface CompletionHint {
  * can naturally suggest the next step without PICA dictating the conversation.
  * If no hints are provided, the response is identical to the old format.
  */
-export declare function formatSuccess(message: string, data?: any, completionHints?: CompletionHint[]): FormattedResult;
+export declare function formatSuccess(
+  message: string,
+  data?: any,
+  completionHints?: CompletionHint[],
+): FormattedResult;
 /**
  * Map raw gap objects from the completeness API into CompletionHints.
  * The API response shape varies — this handles the known field names.
  */
-export declare function mapGapsToHints(gaps: any[], limit?: number): CompletionHint[];
+export declare function mapGapsToHints(
+  gaps: any[],
+  limit?: number,
+): CompletionHint[];
 /**
  * Format array of items with count
  */
-export declare function formatList<T>(items: T[], metadata?: Record<string, any>): FormattedResult;
+export declare function formatList<T>(
+  items: T[],
+  metadata?: Record<string, any>,
+): FormattedResult;
 /**
  * Truncate text to max length
  */
@@ -49,15 +59,24 @@ export declare function truncate(text: string, maxLength?: number): string;
 /**
  * Format validation error
  */
-export declare function formatValidationError(fields: Record<string, string>): FormattedResult;
+export declare function formatValidationError(
+  fields: Record<string, string>,
+): FormattedResult;
 /**
  * Format structured response with dual content blocks:
  * - Human-readable text (includes full JSON so all MCP clients can read it)
  * - Machine-parseable structuredContent object
  */
-export declare function formatStructured(data: any, summary?: string): FormattedResult;
+export declare function formatStructured(
+  data: any,
+  summary?: string,
+): FormattedResult;
 /**
  * Format a list with both human summary and structured JSON
  */
-export declare function formatStructuredList<T>(items: T[], entityName: string, metadata?: Record<string, any>): FormattedResult;
-//# sourceMappingURL=formatting.d.ts.map
+export declare function formatStructuredList<T>(
+  items: T[],
+  entityName: string,
+  metadata?: Record<string, any>,
+): FormattedResult;
+//# sourceMappingURL=formatting.d.ts.map

package/package.json

@@ -1,6 +1,7 @@
 {
   "name": "@withpica/mcp-server",
-  "version": "2.4.0",
+  "mcpName": "io.github.withpica/pica",
+  "version": "2.4.2",
   "description": "MCP Server for PICA Platform - enables AI assistants to interact with PICA",
   "type": "module",
   "main": "dist/index.js",

package/server.json

@@ -0,0 +1,30 @@
+{
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
+  "name": "io.github.withpica/pica",
+  "description": "193 tools for music catalog management — works, recordings, credits, royalties",
+  "repository": {
+    "url": "https://github.com/withpica/pica",
+    "source": "github",
+    "subfolder": "mcp-server"
+  },
+  "version": "2.4.1",
+  "packages": [
+    {
+      "registryType": "npm",
+      "identifier": "@withpica/mcp-server",
+      "version": "2.4.1",
+      "transport": {
+        "type": "stdio"
+      },
+      "environmentVariables": [
+        {
+          "description": "Your PICA API key — get one at https://connect.withpica.com",
+          "isRequired": true,
+          "format": "string",
+          "isSecret": true,
+          "name": "PICA_API_KEY"
+        }
+      ]
+    }
+  ]
+}

package/.vercel/README.txt

@@ -1,11 +0,0 @@
-> Why do I have a folder named ".vercel" in my project?
-The ".vercel" folder is created when you link a directory to a Vercel project.
-
-> What does the "project.json" file contain?
-The "project.json" file contains:
-- The ID of the Vercel project that you linked ("projectId")
-- The ID of the user or team your Vercel project is owned by ("orgId")
-
-> Should I commit the ".vercel" folder?
-No, you should not share the ".vercel" folder with anyone.
-Upon creation, it will be automatically added to your ".gitignore" file.

package/.vercel/project.json

@@ -1 +0,0 @@
-{"projectId":"prj_VIilfoTOeMY9J2GDyajT21axzHkB","orgId":"team_pohaSdNk3LrHAeSjiaF9DRzC","projectName":"mcp-server"}