Install for Claude Code

Build the extension first

Build and install the extension from source first (Quickstart); there is no published .ablx yet. The bridge runs inside Live; this page only wires Claude Code to it. With Live running, the extension has written a bridge.json (a port and a bearer token) into its storage directory.

Connect

Loophole is an HTTP server on loopback, so you add it as an http transport, not a spawned command. Use the exact port and token from bridge.json.

claude mcp add --transport http loophole http://127.0.0.1:<port>/mcp
# then attach the header: Authorization: Bearer <token-from-bridge.json>
claude mcp list   # loophole should appear

Confirm the exact header flag against your installed Claude Code version; the header carries Authorization: Bearer <token>.

The skill writes this for you

Install the ableton-live skill (a thin /doctor + /setup + recipes layer):

npx skills add OthmanAdi/loophole --skill ableton-live

The ableton-live skill (alias loophole) reads bridge.json and writes this config for you:

• /doctor checks the prerequisites (Live running, extension installed, port reachable, token present) and prints exactly what to fix.
• /setup reads the port and token and emits the correct Claude Code config. It never invents a port or token; if bridge.json is missing it tells you to run /doctor first.

Verify it worked

1. Live 12.4.5b Suite is running with the Loophole extension active.
2. claude mcp list shows loophole.
3. Ask the assistant to run live_get_song_overview (or live_find_track) and confirm it returns your real track names.

If the tool returns your actual tracks, the connection is correct. Otherwise see Troubleshooting.