@withpica/mcp-server/dist/tools/consent.d.ts

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

/**
 * Consent MCP Tools — ADR-300.
 *
 * The read side of ADR-292's consent ledger. One tool: the org-level
 * readiness verdict with named blockers.
 *
 * There is deliberately NO write tool here. Consent writes are human-session
 * only — the per-subject consent routes (/api/admin/consent/{people,works,
 * recordings}/[id]) refuse Bearer callers by design, because a consent
 * decision has to be made by the person whose rights it binds, not by an
 * agent acting on their behalf. That refusal is pinned by the ADR-292
 * holdout; do not "fix" it by adding a tool here.
 *
 * Pricing: FREE (read tier).
 */
import { PicaClient } from "@withpica/mcp-sdk";
import type { ToolDefinition, ToolExecutor } from "./index.js";
export declare class ConsentTools {
    private pica;
    constructor(pica: PicaClient);
    getTools(): Array<{
        definition: ToolDefinition;
        executor: ToolExecutor;
    }>;
    private readiness;
}
//# sourceMappingURL=consent.d.ts.map