Skip to content
    ← Back to home

    Solutions

    Automate lighting through the WavePhase HTTP API

    On Pro and Studio, WavePhase exposes an HTTP API and MCP server so external software or agents can supply typed values and triggers. OSC, MIDI, and DMX input remain available as parallel control paths. The graph stays the source of truth.

    Control paths that coexist

    • HTTP API / MCP (Pro+)

      External software or agents post typed values and triggers into source nodes. The graph stays the source of truth — this is not a cloud lighting service.

    • OSC and MIDI

      Consoles, DAWs, and controllers. MIDI in is on every tier; OSC unlocks on Artist and above.

    • DMX input merge

      Paid tiers can take a physical desk as override while WavePhase holds the reactive layer.

    • Web Control

      Humans who should not open the editor get a phone or browser surface on LAN or Cloud relay.

    External control that coexists

    1. 01API/MCP posts values into source nodes (Pro+).
    2. 02OSC and MIDI for consoles, DAWs, and controllers.
    3. 03DMX input merge on paid tiers for a physical desk.
    4. 04Web Control for humans who should not open the editor.

    Integrator examples

    • Show-control computer

      A playback machine sends cues as API triggers while WavePhase owns fixture output.

    • Agent-assisted patching

      MCP lets an assistant inspect and drive pins — patch-building help, not musical-structure claims.

    • Hybrid desk

      Keep DSP-reactive looks in the graph; let a console take over via DMX in when a guest LD arrives.

    Documentation

    FAQ

    Get WavePhase Free

    Free account required — no credit card — Windows, macOS and Linux.

    See all automation modes →