What the offline tools actually read
A saved Live set contains project structure, MIDI and references to devices and samples. AbletonMCP parses that saved information. It does not render audio, hear how a track sounds, or discover unsaved changes in an open Live set.
1. Connect your local MCP client
Follow the Codex connection guide or general setup guide. For offline-only work you can skip Remote Script installation and the socket doctor check. A startup warning about Live being closed does not prevent offline tools from working.
Optionally set ABLETON_TOOLSETS=offline in the MCP server environment to expose only the offline group. Restart the server after changing its environment.
2. Start with a read-only summary
Use als_summary on the .als file at the absolute path I provide. Summarize tracks, tempo, devices and clips. Do not modify files or upload the project.Then use als_lint for structural warnings and als_details for mixer and arrangement detail. A warning is a lead to inspect, not proof that the project is broken or unfinished.
3. Compare two saved versions
Compare these two saved .als files with als_diff. Explain track, device and clip differences, and distinguish saved metadata from anything that needs listening.This is useful before reopening an old idea or reviewing a collaborator's revision. Keep originals intact. Use als_extract_midi when you need note data, and adg_analyze to inspect a saved rack's contents and references.
Know the limits
- Missing external sample paths may reflect a different computer, not lost audio.
- A device list does not prove a plugin is installed, licensed or sounds correct.
- Key detection is an estimate from notes; it is not an audio measurement.
- The bridge does not upload your project, but tool results may be processed by your AI client/provider.