Touchdesigner Mcp Driver

The problem

Controlling TouchDesigner from external scripts or agents usually requires writing custom Python extensions or WebSocket listeners inside the project. Managing node wiring and parameter animation remotely is often brittle and lacks a standard interface.

What it does

• Lists and queries the active TouchDesigner operator network as JSON.
• Creates new TOP, CHOP, SOP, and MAT operators at runtime.
• Wires nodes together by defining input and output connections.
• Animates parameters over specified time intervals with keyframes.
• Triggers frame-accurate image sequence renders directly from the network.

Frameworks & tools

TouchDesigner, twozero MCP extension, td-mcp CLI, and Python.

Why this beats prompting it yourself

This skill handles the specific syntax of the twozero MCP bridge, ensuring proper path formatting and operator family mapping. It manages the connection state and provides a structured way to read back current operator states that standard LLM prompting would miss without a dedicated driver.

Use cases

• Automate generative visual variations for live performance control.
• Script complex render passes for large-scale installation assets.
• Query node parameters to verify the state of a running project.
• Rapidly prototype operator networks via CLI commands.

Known limitations

Requires an active TouchDesigner instance with the twozero MCP extension installed. Not suitable for GPU-less headless environments or deterministic audio-reactive timing.