Getting started
Chromatik MCP
curl -L --create-dirs -o ~/Chromatik/Packages/chromatik-mcp.jar \ https://github.com/oveddan/chromatik-mcp/releases/latest/download/chromatik-mcp.jar# enable Chromatik-MCP in Preferences → Plugins, restart, then:claude mcp add --transport http chromatik "http://127.0.0.1:$(jq -r .port ~/.chromatik-mcp/status.json)/mcp"Any MCP client — Claude Code, Claude Desktop, Cursor, your own orchestrator — connects straight into the running engine: the agent reads and mutates the same instance your console renders, no project-file editing or reload cycle.
Parse the scene
Section titled “Parse the scene”A project you inherited is a few thousand parameters deep, and “how is this wired” is an answer spread across channels, modulators, and mappings. The agent walks the whole tree and tells you.
I just opened this project. How is it put together?
Eight channels on the master bus; the top three are grouped as Structure and blend Screen over a static base. Two LFOs and a beat follower drive nine modulation mappings — mostly speed and brightness on that group. The palette runs a four-swatch cycle that six of the patterns read from, so they shift together. Two channels are muted, and one — Drop — is a trigger-only blend parked at zero.
What does the Drop channel do — and how is it triggered?
It’s your payoff moment: a blend channel that sits dark until triggered — by a MIDI note from the song, or pad A16 on your controller. Either one fires an envelope that takes the channel to full in 250ms, holds two seconds, and eases out over three — retriggering five effect envelopes on the way up.
What can I map from the lighting console over OSC?
Every parameter here has an OSC address. Here are the forty on your active patterns — starting with the ones already in motion.
From a session on a live rig the agent had never seen.
Start here
Section titled “Start here”Connect your AI client
Tool reference
Driving Chromatik well
Architecture
Usage examples