@withpica/mcp-server/dist/tools/profile-claims.d.ts

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

/**
 * Profile Claims Tools: claim your profile, for assistants (founder decision
 * 2026-10-03: assistants may send and check claim invites).
 *
 *   - pica_profile_claims_invite: invite people in this catalogue to claim
 *     their profile, at the address the catalogue holds for each. A PREVIEW
 *     unless `confirm: true`: inviting emails real people, so the assistant
 *     shows the person it acts for who would be emailed, then calls again.
 *     Only a credential that belongs to an owner or admin may send; an
 *     organisation key with no owner is refused (INVITE_REQUIRES_PERSON).
 *     Declared approvalMode "human" (spec claim-your-profile phases 2–4
 *     §4.7): from a connected app or agent grant the call sends nothing and
 *     is held for the grant owner to approve; the approved call is replayed
 *     by human-approval-executor.ts. The route behind it refuses those
 *     callers directly (INVITE_NEEDS_APPROVAL), so this stdio server on a
 *     grant cannot skip the hold either.
 *   - pica_profile_claims_status: where people stand (claimed, invited and
 *     waiting, expired, sent to an address since changed, answered "not me"
 *     or "I manage them", not invited). Never returns an email address.
 *
 * Both call the same routes the people list and person page use
 * (POST /api/admin/people/claim-invites, GET /api/admin/profile-claims), so
 * every rule the app applies applies here.
 */
import { PicaClient } from "@withpica/mcp-sdk";
import { ToolDefinition, ToolExecutor } from "./index.js";
export declare class ProfileClaimsTools {
    private pica;
    constructor(pica: PicaClient);
    getTools(): Array<{
        definition: ToolDefinition;
        executor: ToolExecutor;
    }>;
    private invite;
    private status;
}
//# sourceMappingURL=profile-claims.d.ts.map