data-ai MCP Server
Local-first beat library for music producers. MCP server (Claude Code / Claude Desktop) for AI-driven cataloging, tagging, and multi-platform publishing.
Discovered via github-topic:claude-mcp and last synced 3mo ago.
Install instructions not detected yet
Check the source repository for the latest setup steps.
Tools
**Why two-phase commit?** Every write tool returns a `token` (preview only) — nothing touches the database. The token surfaces in the **Agent Actions panel** in BeatOS; you review the diff, then confirm. The agent calls `await_approval` to learn the outcome. By default **an AI can never silently mutate your catalog**, batch-edit your producer credits, or trash a track without you signing off — unless you deliberately switch the permission setting to auto-approve (or lock it to read-only). **Why batches?** A folder-import of 50 tracks × 2 audio assets would otherwise be 100 approval clicks. `create_tracks` (≤100), `attach_assets` (≤500), `detach_assets` (≤500) all batch — one token, one click, atomic rollback if any file vanishes mid-approve. **Example flow** (driven by Claude Code from your terminal): ```text You: "Tag every beat above 140 BPM that has no genre with 'Trap' or 'Drill' based on the cover art and title. Show me the diff before applying." Claude: [calls list_tracks(bpm_min=140) → 12 tracks] [reads metadata, drafts a patch] [calls update_tracks(items=[...]) → returns token abc123] You: [opens BeatOS Approvals panel, sees 12 proposed edits with rationale] [reviews 3, rejects 1, approves the batch] Claude: [await_approval → status=approved, applies, reports back] ``` The same pattern drives on-demand per-platform metadata export today, and will drive publish drafts (Pro) and self-corpus RAG drafts (v0.3+). ## Local-first, by design