touchdesigner-mcp

Control TouchDesigner via twozero MCP to create operators, set parameters, and wire connections.

Updated May 26, 2026
One-click install
npx skills add https://github.com/ruiyangruiyi/hermes-agent --skill touchdesigner-mcp-ruiyangruiyi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: touchdesigner-mcp
Source: https://github.com/ruiyangruiyi/hermes-agent/tree/main/skills/creative/touchdesigner-mcp
Command: npx skills add https://github.com/ruiyangruiyi/hermes-agent --skill touchdesigner-mcp-ruiyangruiyi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill solves the problem of controlling a running TouchDesigner (TD) instance programmatically without brittle, version-dependent hacks for operator creation, parameter setting, wiring, and shader/visual execution.

Core Features & Use Cases

  • MCP-based TouchDesigner control loop: Drive TD through twozero MCP over localhost, including discovery, building, inspection, and screenshot capture workflows.
  • Version-safe operator building: Uses TD discovery-first rules (e.g., never guess parameter names; fetch param metadata before setting) and guardrails that stop on attribute/op failures.
  • Creative-coding workflows: Create operators, set parameters, wire networks, run Python when needed, and support real-time visuals such as audio-reactive GLSL setups.

Use cases include: building generative/GLSL node chains, creating deterministic TD networks for repeatable installations, automating operator setup (including cleanup + rebuild in safe call ordering), and validating outputs by checking errors/warnings and capturing screenshots.

Quick Start

Run: bash "${HERMES_HOME:-$HOME/.hermes}/skills/creative/touchdesigner-mcp/scripts/setup.sh" to verify twozero MCP availability and register the MCP server in Hermes.

Frequently Asked Questions about touchdesigner-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate TouchDesigner operator creation and parameter setting without version-dependent hacks?

Automating TouchDesigner networks is handled by controlling a running instance through twozero MCP, using discovery-first parameter fetching to safely create operators, set parameters, and wire connections without guessing parameter names.

Can I build audio-reactive GLSL visual pipelines in TouchDesigner programmatically?

Building audio-reactive GLSL setups is supported by driving TouchDesigner through MCP calls to construct node chains, execute TD-side Python, and validate real-time visual outputs via screenshot capture.

How do I safely clean up and rebuild a TouchDesigner network across sessions?

Safe cleanup and rebuild sequencing in TouchDesigner is achieved by using separate MCP calls for destruction and construction, ensuring the process stops immediately on any TD attribute or operator errors.

Does TouchDesigner MCP require a localhost health check before connecting?

A localhost MCP health check is required before connecting, verifying twozero MCP availability to ensure the TouchDesigner control loop can execute discovery, building, and inspection workflows safely.

What is the best way to inspect TouchDesigner parameters before modifying them?

Inspecting TouchDesigner parameters requires a discovery-first approach using td_get_par_info and td_get_hints to fetch parameter metadata, preventing brittle failures from guessing parameter names.

Why does my TouchDesigner automation script stop on attribute errors?

TouchDesigner automation stops on attribute errors due to strict failure guardrails that prevent unsafe execution, ensuring TD-side Python and operator wiring do not proceed with missing or invalid components.