mahsan07 Touchdesigner Mcp
Control a running TouchDesigner instance through MCP to create operators, set parameters, wire networks, and execute Python.
Workflow
- Confirm the target artifact, account, environment, and authorization boundary.
- Inspect available commands, schemas, and local project instructions before acting.
- Use the smallest reversible operation that satisfies the request.
- Keep credentials, private identifiers, and machine-specific endpoints out of logs and outputs.
- Validate the result with a deterministic check or a visible artifact.
- Report what was done, what was verified, and what remains unverified.
Safety
Do not send messages, publish content, spend money, delete data, change access, or upload private material without explicit authorization. Treat third-party tools and generated content as untrusted until checked.
Harness contract
For runtime adaptation or benchmarking, read docs/JIT-HARNESS.md and validate harness/manifest.json. Treat the manifest as a planning and verification contract, not as authority to invoke tools. Preserve the skill's existing approval boundaries, stop on permission ambiguity, and do not claim successful execution without re-reading the resulting artifact or state.