MCP server for TouchDesigner
MCP server for TouchDesigner. That is what the touchdesigner mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
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.
TouchDesigner MCP acts as a bridge between AI models and the TouchDesigner WebServer DAT, enabling AI agents to:
The server publishes 14 tools. What each one is for:
create_td_node — Creates a new nodedelete_td_node — Deletes an existing nodedescribe_td_tools — Generates a manifest of the available TouchDesigner toolsexec_node_method — Calls a Python method on a nodeexecute_python_script — Executes an arbitrary Python script in TouchDesignerget_td_class_details — Gets details of a TouchDesigner Python class or moduleget_td_classes — Gets a list of TouchDesigner Python classesget_td_info — Gets information about the TouchDesigner server environmentget_td_module_help — Gets Python help() documentation for TouchDesigner modules/classesget_td_node_errors — Checks for errors on a specified node and its childrenget_td_node_parameters — Gets the parameters of a specific nodeget_td_nodes — Gets nodes under a parent path, with optional filteringSetup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Touchdesigner MCP's toolset — create_td_node, delete_td_node, describe_td_tools and 11 more — is a fair guide to whether it matches your workflow. It is maintained by 8beeeaaat; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Touchdesigner MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| create_td_node | Creates a new node. |
| delete_td_node | Deletes an existing node. |
| describe_td_tools | Generates a manifest of the available TouchDesigner tools. |
| exec_node_method | Calls a Python method on a node. |
| execute_python_script | Executes an arbitrary Python script in TouchDesigner. |
| get_td_class_details | Gets details of a TouchDesigner Python class or module. |
| get_td_classes | Gets a list of TouchDesigner Python classes. |
| get_td_info | Gets information about the TouchDesigner server environment. |
| get_td_module_help | Gets Python help() documentation for TouchDesigner modules/classes. |
| get_td_node_errors | Checks for errors on a specified node and its children. |
| get_td_node_parameters | Gets the parameters of a specific node. |
| get_td_nodes | Gets nodes under a parent path, with optional filtering. |
| get_top_image | Captures the current output of a TOP node as an image. |
| update_td_node_parameters | Updates the parameters of a specific node. |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.