reklawdbox

Your first three choices

1. Install and connect

   Choose the supported Homebrew or source-build path, configure your host, then reconnect it.

   InstallInstall the binary, connect Claude Code, Claude Desktop, or Codex, and verify the host setup.

2. Get one safe first result

   Ask for a bounded library summary using one read-only, local tool. This confirms the connection before you choose a larger workflow.

   First 10 minutesCopy one read-only prompt and understand exactly what it does not change.

3. Choose a goal with the trade-offs visible

   Compare collection impact, direct file writes, local state, outputs, and prerequisites before opening a workflow.

Already know what you need? Browse all workflows →

Safe by design

reklawdbox never writes to your Rekordbox database. Rekordbox metadata changes are staged in memory and exported as XML for manual import. File-tag and artwork tools are a separate, direct-write path, and the application also creates local cache, backup, configuration, and export files.

• Read-only database access — your master.db is never modified
• Staged Rekordbox metadata — preview or discard metadata changes before export
• Explicit file operations — preview tag writes when available and review every target
• Scoped host permissions — keep normal prompts enabled and grant only what a workflow needs

Safety & TrustThe boundaries for master.db, staged metadata, direct file writes, local state, and host permissions.