touchdesigner-mcp

8beeeaaat/touchdesigner-mcp is ranked 3,200 among these 8 peers; puran-water/autocad-mcp is ranked 3,206.

TouchDesigner MCP This is an implementation of an MCP (Model Context Protocol) server for TouchDesigner. Its goal is to enable AI agents to control and operate TouchDesigner projects. If you are updating, please refer to the procedure in the **Latest Release**. MCP Server Features This server enables AI agents to perform operations in TouchDesigner using the Model Context Protocol (MCP). Tools Tools allow AI agents to perform actions in TouchDesigner. | | | Generates a manifest of the available TouchDesigner tools. | | | Executes an

arbitrary Python script in TouchDesigner. | | | Gets details of a TouchDesigner Python class or module. | | | Gets a list of TouchDesigner Python classes. | | | Gets information about the TouchDesigner server environment. | | | Gets Python help() documentation for TouchDesigner modules/classes. | | | Checks errors **and warnings** on a node and its descendants. Missing files, dangling references and shader failures are warnings, so no errors does not mean healthy. | | | Gets the parameters of a specific node. | | | Gets nodes under a parent path, with optional filtering. | | | Captures the

current output of a TOP node as an image. | | | Updates the parameters of a specific node. | Prompts Prompts provide instructions for AI agents to perform specific actions in TouchDesigner. | | | Provides instructions to connect nodes within TouchDesigner. | | | Checks errors and warnings on a specified node, and recursively for its descendants. Developer Guide Looking for local setup, client configuration, project structure, or release workflow notes? See the **Developer Guide** for all developer-facing documentation. Troubleshooting Troubleshooting version compatibility The MCP server and

the TouchDesigner component are versioned on **two independent axes**: the npm package version and the **API version** (the contract between the MCP server and the component). Each release declares the API version it ships with ( ) and the minimum it supports ( , currently 1. Download the latest touchdesigner-mcp-td. Delete the existing folder and replace it with the newly extracted contents. Remove the old component from your TouchDesigner project and import the from the new folder. Restart TouchDesigner and the AI

agent running the MCP server (e. **For developers:** When developing locally, run after editing (or simply use ). This keeps the Python API ( + ), , MCP bundle manifest, and registry metadata in sync so that the runtime compatibility check succeeds. For a deeper look at how the MCP server enforces these rules, see Version Compatibility Verification. Troubleshooting connection errors caches failed connection checks for **60 seconds**. Subsequent tool calls reuse the cached error to avoid spamming TouchDesigner and automatically retry after the TTL

expires. When the MCP server cannot reach TouchDesigner, you now get guided error messages with concrete fixes: / "connect refused": start TouchDesigner, ensure the WebServer DAT from is running, and confirm the configured port (default ). / "timeout": TouchDesigner is responding slowly or the network is blocked. Restart TouchDesigner/WebServer DAT or check your network connection. The structured error text is also logged through , so you can check the MCP logs to understand why a request stopped before hitting TouchDesigner. Contributing We welcome

your contributions! Add tests and ensure everything works ( ). Please always include appropriate tests when making implementation changes.