@withpica/mcp-server/dist/tools/recording-samples.d.ts

MCP Server for withPICA — enables AI assistants to interact with your withPICA music catalog

/**
 * Recording Samples MCP Tools — ADR-259 (provenance thread)
 *
 * Four tools exposing marketplace sample provenance per recording (Splice,
 * Tracklib, etc.) — which sample went into a recording, from where, and its
 * clearance posture. Thin wrappers around this.pica.recordingSamples.* which
 * calls the HTTP routes under /api/admin/recordings/{id}/samples.
 *
 * Tools:
 *   pica_recording_samples_list       — list the logged samples (read)
 *   pica_recording_samples_add        — log a sample (write, idempotent)
 *   pica_recording_samples_set_status — update clearance status (write)
 *   pica_recording_samples_remove     — remove a sample entry (write)
 *
 * Org-scoping is enforced at the HTTP route layer: every route verifies the
 * recording belongs to the caller's org before touching recording_samples.
 * clearance_status defaults to 'unknown' (ADR-264 honest-by-default; absence
 * never means cleared).
 *
 * Pricing: FREE. ADR-162 deprecates credit gating as a user-facing concept.
 */
import { PicaClient } from "@withpica/mcp-sdk";
import type { ToolDefinition, ToolExecutor } from "./index.js";
export declare class RecordingSamplesTools {
    private pica;
    constructor(pica: PicaClient);
    getTools(): Array<{
        definition: ToolDefinition;
        executor: ToolExecutor;
    }>;
    private list;
    private add;
    private setStatus;
    private remove;
}
//# sourceMappingURL=recording-samples.d.ts.map