THE DAW HORSEMEN
OF THE APOCALYPSE

MCP Survival Pack v2.6.0 - tray companion, MSI, CARE heal, four DAWs, shared Bitwig SSE.

Tracker grids. Clip launchers. Envelope points. Reason racks inside REAPER. Cursor, Claude, and friends on the same wire.

Download MSI Open the repo Install / CARE / GUI DAW primers Credits

SCROLL FOR THE RIDE

THE FOUR RIDERS

Each horseman is a real DAW surface your agents can touch — not a metaphor bolted on after the fact. Below: what it feels like, what the MCP can drive, and who built the upstream.

DEATH
REAPER

ENVELOPES, ITEMS, THE FULL HARVEST

The pale rider does not dabble. Tracks, takes, MIDI notes, FX chains, sends, sidechains, markers, regions, renders — the arrange page as a battlefield map. When an agent draws an envelope, you should feel the point land on the lane, not a vague “set volume” shrug.

Python MCP talks to a stock Lua bridge inside REAPER. No mystery network stack: file/HTTP handshake, then 100+ tools aimed at real mixing and writing sessions.

Primer — what to ask for
  • Build a bus, parallel compress a vocal, or wire a kick→bass sidechain in one call
  • Drop MIDI, edit velocities, split items, fade edges, park markers/regions
  • Walk FX params by index, flip presets, arm a render-by-region
  • Ask for get_project_summary when the agent needs the whole desk at once
packages/reaper-mcp/

Upstream: TwelveTake Studios LLC · MIT

WAR
BITWIG

CLIP LAUNCHERS, SCENES, ONE OSC SWORD

War rides the clip launcher grid — scenes firing, pads lighting, transport locked — while the arrange timeline still matters. Bitwig’s OSC controller only answers one process. Spawn a second MCP and you fight over UDP 9001 like rival generals with one radio.

This pack’s fix: a shared HTTP-SSE server. Cursor, Claude Code, Claude Desktop, VS Code — all point at the same socket. DrivenByMoss (DawpocalypseMCP fork) holds the OSC lance; the Python MCP swings it.

Primer — what to ask for
  • Transport, tempo, track volume/pan/mute, device parameters
  • Launcher clips & scenes (select, launch, record, duplicate)
  • Device browser / recommend / Poly Grid helpers where indexed
  • Always run run_bitwig_mcp_shared.bat first; agents use http://127.0.0.1:8080/sse
packages/bitwig-mcp-server/

Upstream: John Stanford (jxstanford) · OSC/MCU: Jürgen Moßgraber / DrivenByMoss

PESTILENCE
RENOISE

PATTERN EDITOR, HEX COLUMNS, PHRASE DISEASE

Pestilence lives in the pattern editor — note columns, instrument numbers, volume/pan/delay hex, effect columns chewing DSP. Agents do not “draw a melody on a piano roll” here; they write tracker language: lines, phrases, pattern order, phrase aliases, instrument slots.

ReMCP runs inside Renoise (HTTP). The pack’s Node bridge only translates stdio MCP clients into that stream. Start the tool panel, hit Play if focus-loss starves the server, then let the agent infest the grid.

Primer — what to ask for
  • Song info, BPM/LPB/TPL, transport play/stop/panic
  • Tracks, patterns, sequencer order, instruments, devices
  • Pattern lines & note data the way a tracker musician thinks
  • Renoise: Tools → Renoise MCP → Start; bridge retries until it answers
packages/renoise-mcp-bridge/

Upstream: ReMCP by kraken · renoise/tools

FAMINE
REASON

NO MCP OF ITS OWN — RIDES THE RACK

Famine starves for a native MCP. So it hitchhikes: load Reason as a Rack Plugin (or Rewire-era habit) inside REAPER, and Death’s tools drive the session around it — tracks, FX outside the rack, MIDI into the rack, renders out.

Honest primer: you are not remote-controlling Reason’s Combinator knobs via a Reason-specific protocol. You are producing around Reason with REAPER MCP muscle. That is still a full apocalypse for songwriting.

Primer — what to ask for
  • Create REAPER tracks that host / feed the Reason rack
  • Route MIDI, set up buses, mix the outs beside the rack
  • Keep Reason sound design manual; let the agent own the session scaffolding
packages/reason/

Control rides TwelveTake REAPER MCP — no separate Reason MCP upstream

ONE WAR, MANY GENERALS

Bitwig’s OSC surface is a single sword. The pack ships run_bitwig_mcp_shared.bat so Claude CLI, Cursor, VS Code MCP extensions, and Claude Desktop all command the same battlefield instead of fistfighting over UDP 9001.

http://127.0.0.1:8080/sse

OSC ports that must stay honest: receive 8005 / send 9001 on DawpocalypseMCP (DrivenByMoss Open Sound Control). CARE/INSTALL heal those prefs. Full IDE wiring: IDE_SETUP.txt.

THE SUMMONING

Clone once. Heal always. Loose copies are heresy — the GitHub repo is the source of truth. Or grab the release ZIP and double-click the GUI.

git clone https://github.com/aday1/The-DAW-Horsemen-of-the-apocalypse-MCP-survival-Pack.git DAW-Horsemen cd DAW-Horsemen launch_daw_mcp.bat :: Tkinter GUI (CARE / heal / stacks / health) CARE.bat :: CLI: pull-if-behind + heal OSC/paths/Mackie + shortcut + health

CARE.bat always heals. INSTALL.bat = deps+heal. UPDATE.bat = git pull+heal. Wire IDEs with IDE_SETUP.txt. Behringer X-Touch is MCU MIDI beside MCP — see packages/mackie-xtouch/SETUP_MACKIE.txt. Showcase (this page): aday1.github.io/...Horsemen.../ · Release: v2.6.0 MSI.

UPDATE.bat :: checks GitHub, pulls if behind, refreshes deps RELEASE.bat :: maintainer: ZIP + GitHub release from HEAD PUBLISH.bat :: maintainer: push committed work

CREDITS — UPSTREAM RIDERS

This pack wires other people’s work. Names first; packing second.