touchdesigner-mcp

You can automate real-time TouchDesigner scene control by using MCP tools to drive operator creation, parameter discovery, wiring, and verification directly within a running instance. This approach replaces guesswork with deterministic, tool-driven network construction.

Yes, you can build audio-reactive GLSL visuals by instructing the agent to create GLSL TOPs and wire them to audio analysis operators via MCP. The Skill supports real-time parameter updates and shader-driven pipelines for live VJ-style performances.

The best way to discover valid parameters is by running TD-native introspection calls like td_get_par_info and td_get_hints before modification. This strict pre-discovery ensures parameter names and workflows match your specific TouchDesigner version.

TouchDesigner MCP control requires local-only connectivity established through a configured localhost port. You must run the scripted setup command to connect your running TouchDesigner instance to the MCP server before executing any operator commands.

Operator creation fails when you skip guarded execution steps like td_get_operator_info and td_get_errors. To avoid invalid OP references and common TD pitfalls, you must perform strict pre-discovery and verify results after creating and wiring operators.

You can automate rendering and screenshot capture by using MCP tools to trigger record and screenshot workflows within your live TouchDesigner instance. This supports automated render exports for generative art and audio-reactive visual pipelines.