LiveSet · AI-assisted authoring
The assistant inside LiveSet
LiveSet ships a Model Context Protocol server inside the packaged app. It gives an AI assistant over a hundred tools to read your project, understand your sounds and write into the running set. You say what you want in plain language. The app redraws as it writes. You still play the set.
What it can see
The tools speak in decks, slots, patterns, scenes and parameters, so an assistant works at the level you do, and they can read the current state of the set before they change any of it.
Read the set back
Ask what is loaded and it answers: the decks, the slots, the patterns, the scenes, the effects on a track. It reads the live project state, so a saved file never goes stale under it.
Introspect the sound
It can walk a synth voice or an effect and report the parameters, their ranges and their current values, so a change is made in full knowledge of what is there.
Author and edit
It writes components, patterns and automation, and changes what already exists. These are the same edits you would make on screen.
Undo in one step
Work runs inside transactions. Each authoring operation is a single undo entry, so a change you dislike comes back off with one undo.
Describe and draw
Authoring by description
Describe a liveset in a sentence: a rolling bassline, a pad on the second deck, a break every eight bars. The assistant builds it by calling the same edits the on-screen controls call, so nothing reaches your project through a side door.
Because it uses the same edits, the app knows what changed and redraws while the assistant writes. You watch the patterns, the scenes and the parameters fill in, and you can take over the moment you want to.
Your own tools
Scripting the surface
The same tools are yours to build on. If a task is repetitive, laying out a scene the way you always do, prepping a deck to a house pattern, you can script it against the set and have the assistant carry it out. The MCP is a working interface to the project, so what you can describe, you can automate.
A request, roughly
you · "add a deep-house bassline on deck B"
↳ read state · list decks, slots, scenes
↳ author · pattern + synth component
↳ author · automation on the filter
↳ one transaction · one undo entry
↳ app redraws as it writes
Who does what
What it does, and what stays yours
This is an authoring assistant, and the performer is still you. It writes and changes the set: components, patterns, automation, whole livesets from a sentence. What it does not do is take the stage. It is there to build and rework the material around your hands.
Where it runs
The way it runs is built to be quiet and local by default.
In the packaged build
The MCP server is bundled inside the installed app. It is part of the shipping product, with no separate add-on to buy.
Off by default, local only
The live interface starts switched off. When you turn it on it listens only on your own machine, at 127.0.0.1, and needs a token before anything connects.
A headless mode
There is also a detached mode that writes .liveset files offline, with no running app to connect to. Author a set, then open it later.
What it reaches
How much of the set it reaches
Reading the set, introspecting it and authoring into it all work, including building a liveset from a description straight into the running app. Two jobs stay in the app itself: installing live MIDI bindings, and loading samples and other assets. Those are hands on the hardware and the filesystem, so you do them there.