
othmanadi/loophole
Developer tools이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기
Control Ableton Live from Claude and any LLM. An MCP server built on Ableton's official Extensions SDK: one .ablx, no Remote Script, no AbletonOSC, no Max for Live. TypeScript, Live 12.4.5 Suite beta.
개요
It is designed to run inside Live on Ableton's official Extensions SDK, which makes it No Remote Script, no AbletonOSC, no Max for Live. Read the versioned source documentation in docs/src/content/docs. There is no published package, .ablx, CLI, or release yet. Loophole is two things that feed each other: - a small set of focused Ableton extensions for the chores that eat studio time (arrangement, gain staging, set hygiene, scale, groove). - an MCP server that lets an LLM (Claude, Cursor, any MCP client) read and edit your Live Set through the same official API the Kit uses. The Kit defines focused producer workflows. The Bridge exposes the shared capabilities to MCP clients. They share one codebase and one local install path. The SDK-free core and MCP library are exercised without Live. SDK typechecking, .ablx packaging, loading in Live, client connectivity, and real undo behavior are separate gates in the E2E checklist. Unchecked gates are NOT_RUN; they are not implied by CI.
README
원문 README의 일부입니다. 원문 보기.
Loophole is the source for an Ableton MCP library and extension kit, built so an MCP client can control Ableton Live through one locally packaged .ablx. It is designed to run inside Live on Ableton’s official Extensions SDK, which makes it the first MCP server built on Ableton’s official Extensions SDK. No Remote Script, no AbletonOSC, no Max for Live.
Read the versioned source documentation in docs/src/content/docs. There is no published package, .ablx, CLI, or release yet.
Loophole is two things that feed each other:
- The Loophole Kit: a small set of focused Ableton extensions for the chores that eat studio time (arrangement, gain staging, set hygiene, scale, groove).
- The Loophole Bridge: an MCP server that lets an LLM (Claude, Cursor, any MCP client) read and edit your Live Set through the same official API the Kit uses.
The Kit defines focused producer workflows. The Bridge exposes the shared capabilities to MCP clients. They share one codebase and one local install path.
Verification boundary. The SDK-free core and MCP library are exercised without Live. SDK typechecking,
.ablxpackaging, loading in Live, client connectivity, and real undo behavior are separate gates in the E2E checklist. Unchecked gates areNOT_RUN; they are not implied by CI.
flowchart LR
kit["Loophole Kitfive context-menu workflows(producers)"]
bridge["Loophole BridgeMCP server (devs, AI)"]
docs["docs + skillguides, tool reference"]
users["usersproducers + builders"]
kit -- "defines focused workflows" --> bridge
bridge -- "tool reference, recipes" --> docs
docs -- "lowers the on-ramp" --> users
users -- "adoption, feedback, more chores to automate" --> kit
classDef accent fill:#E9A23B,stroke:#9A6A1A,color:#160F02,font-weight:bold;
class kit accent;
Where everything lives
설치
npx skills add OthmanAdi/loophole --skill ableton-live