AI Agent Access

Let an AI assistant on your Mac drive Tremor's decks the way a controller does: plan a set from your library, load and analyze tracks, mix beat-locked, scratch, play the drum kit, record. Everything runs on your Mac. Off by default, on with one toggle.

Patent pending: the agent tool layer and its engine-quantized execution are the subject of a pending U.S. patent application.

What it is

Tremor for macOS hosts a Model Context Protocol (MCP) endpoint. MCP is the open standard AI tools use to call other software, so anything that speaks it, Claude Code, Claude Desktop, Cursor and others, can see Tremor's tools and use them. The agent doesn't touch the audio path: it reads your library and each track's structure, then declares what it wants, and Tremor's engine lands every action on the beat grid. That's why a mix an AI asks for arrives exactly on the phrase, even though the AI itself thinks in seconds.

🔒

Local and private

The endpoint is bound to your Mac only (127.0.0.1), protected by a key generated on the machine, and closed the moment you turn the toggle off. There are no accounts and no servers. Your music, your mixes and your conversations with the agent never leave the computer.

Setup

1. Turn it on

Tremor › Settings › General › AI Agent Access › switch on Allow AI agents to control Tremor. The status line below shows the local address and how many tools and prompts are available.

2. Connect Claude Code

Click Copy Setup Command and paste it into Terminal. It registers Tremor's bridge with Claude Code:

claude mcp add tremor -- "/Applications/Tremor.app/Contents/Helpers/tremor-mcp"

Open Claude Code and ask it to list Tremor's tools. From then on it can launch Tremor if it isn't running, browse the library and drive the decks.

3. Connect Claude Desktop or Cursor

Both take the same bridge as a stdio server. In Claude Desktop, open Settings › Developer › Edit Config and add:

{
  "mcpServers": {
    "tremor": {
      "command": "/Applications/Tremor.app/Contents/Helpers/tremor-mcp"
    }
  }
}

In Cursor, add the same entry under Settings › MCP. Restart the client; Tremor appears in its tool list.

💡

Analyze first

An agent plans from each track's structure: phrases, energy curve, where the vocals are. Run analysis over your library once (or ask the agent: "make my library searchable") so every plan is instant and phrase-accurate.

What the agent can do

Dig the crateSearch by text plus BPM window, Camelot key compatibility, minimum energy and mood.

Read the trackSections, phrase starts, the energy curve, vocal regions, BPM and key, the map a DJ builds by ear.

Load and cueLoad onto any of four decks, wait for analysis, seek, set and jump hot cues.

MixDeclare a beat-locked transition: blend or cut at the next phrase, echo-out, filter fade, spinback, brake. The engine executes it.

Shape the soundThree-band EQ and the Sound Color knob per deck; tempo, key shift, sync roles, quantize, slip.

StemsMute, solo or ride the gain of drums, bass, vocals and melody on any deck.

ScratchBaby, chirp, flare, crab, transformer, drag, spinback and more on the platter physics, quantized to the downbeat.

Beat FX and padsTempo-locked effects, including reverse roll on a single stem; sampler pads with loop, quantize and repeat rolls.

Play the kitA licensed drum and instrument kit on its own bus: kicks, hats, claps, 808, quantized to the playing deck.

Record and recapRecord the mix, reconstruct what was played, save it as a playlist.

Things to say

Dig my crate for 130-BPM breaks in 9A, high energy, and plan a twenty-minute build. Load them on A and B and tell me where the drops are. Blend into B over 32 beats at the next phrase, bass swap at the midpoint, and land B's drop on the handoff. Flare scratch on the next downbeat, then echo out. Give me hat rolls and a kick on the two over this breakdown. Mute A's vocals, solo B's drums, and spin B back at the next phrase. What did I play tonight? Save it as a playlist.

Built-in prompts show up in your client as slash commands: /dj_session, /plan_set (a short interview builds the brief, then the booth preps the crate), /crate_dig, /analyze_library, /set_recap.

Good to know

The agent declares, the engine executes. Ask for musical outcomes ("at the next phrase", "on the downbeat") rather than stopwatch timing. Tremor quantizes every action; an agent counting seconds cannot.
Pro features are Pro features. Stems, four decks and video need Tremor Pro whether a human or an agent asks for them.
Streaming content stays streaming. Recording is refused while SoundCloud-sourced tracks are loaded, exactly as it is at the mixer.
First launch after an update compiles the on-device models once (around a minute); the agent will wait for analysis on the first loads.
Turning the toggle off closes the endpoint and revokes the bridge immediately. Turn it on again any time.

Troubleshooting

"Could not launch Tremor" from the client: AI Agent Access is off, or Tremor isn't installed in /Applications. Turn the toggle on, or fix the path in the setup command.
Tools listed but actions do nothing: the app was launched from a different build (for example a debug copy). Quit every Tremor, launch the App Store copy, toggle Access off and on.
Loads report "analyzing" for a long time: the models are compiling on first launch, or the library is large. Let analysis finish once; it's cached after that.
iOS? The endpoint is macOS-only in 3.3. iPhone and iPad get everything the agent's work produces (sets, playlists, cues) through your library.