Building automations with an AI assistantRequires Pro
Let Claude Code, Codex or Cursor read, explain and change your Node-RED flows through Time-line Live's built-in MCP server.
Time-line Live has a built-in MCP server. Turn it on, and an AI assistant on your computer, such as Claude Code, Codex or Cursor, can read your Node-RED flows, explain them, and build or change them for you. You describe what should happen on a keypoint and the assistant will wire the nodes.
Nothing extra needs to be installed. Only apps on this computer can connect, and every change is backed up before it is made.
Turn It On
Open Settings → Network, and find AI assistants (MCP) in the Node-RED section.
Turn on the switch and confirm. Time-line Live starts the MCP server and shows the connection details below the switch.
Assistants can read and change your automations. Every change is backed up first, and an assistant can only change flows through the same checks the Node-RED editor uses, but do read what it did before a show.
Connect an Assistant
The quickest way is the setup prompt:
Click Copy setup prompt.
Paste it into your assistant. The prompt contains the address and token, plus the way each assistant stores a connection, so the assistant adds Time-line Live to its own settings.
Ask something simple to check it worked, such as "What does my Example flow do?"
If you prefer to set it up by hand, open Manual setup under the switch. It shows the address, the token, and a ready-made snippet for each assistant:
- Claude Code: one
claude mcp addcommand. - Codex: a block for
config.toml. - Cursor: a block for
mcp.json. - Other MCP clients: the address and the
Authorizationheader.
The address is http://127.0.0.1:46890/mcp. Treat the token like a password: anyone with it can change your flows from this computer.
What the Assistant Can Do
Read
- List your flows and explain what a flow does.
- Find nodes across all flows, for example every Output that sends to your lighting desk.
- Look up how a node type works, its settings and its defaults.
Change
- Create a flow, add or change nodes, delete nodes or flows.
- Press an Inject node's button, to test a flow.
- List and restore backups. Time-line Live keeps the last 20, one for each change an assistant made.
Every change is checked before it is deployed: the node types must exist, wires must lead somewhere, and a node can only carry the settings its type has. If you changed something in the Node-RED editor in the meantime, the assistant's change is refused rather than overwriting yours; the assistant then reads the flows again and retries.
New nodes are laid out for you: left to right along their wires, with the nodes of a family grouped together. You don't have to tidy up after the assistant.
Prompts to Try
- "What does my Example flow do?"
- "Add a flow that sends the OSC message
/light/strobe 1to 127.0.0.1 port 9000 every time a Drop starts, and/light/strobe 0when it ends." - "Dim the lights during every Breakdown: send
/master 0.2, then ramp back up to 1 over the last 8 seconds before the next section." - "On every beat during a Drop, send
/chase/stepwith the beat." - "Why doesn't my Build flow fire?"
- "Undo the last change you made."
Say which desk or software should receive the messages, and its address and port, the same way you would fill in an Output node. If you have a flow that already talks to it, mention that flow: the assistant reuses its server settings.
For a bigger show, ask for one group per Key Point family, for example "a warm look for the Build family, white for the Drop family, deep blue for the Breakdown family". The assistant builds a block per family, which keeps the flow readable.
If the Node-RED Editor Is Open
When an assistant changes flows while the Node-RED editor is open, the editor shows The flows on the server have been updated with a Review changes button. That is Node-RED's own behaviour for any change made outside the editor.
Click Review changes, then Merge. The assistant's changes appear, and nothing you have open is lost. Reloading the editor works too, as long as you have no unsaved changes of your own.
Turn It Off or Change the Token
- Turn off the switch to stop the server. Connected assistants are cut off straight away.
- Regenerate token (under Manual setup) gives you a new token. Assistants set up with the old one stop working until you give them the new setup prompt. Do this if you think the token has leaked.
The assistant runs on your computer and talks to Time-line Live directly. Your flows are not sent to Time-line, but they are sent to the AI service the assistant uses. Check that service's policy if your flows contain anything private.
How is this guide?
Last updated on