by 8beeeaaat
MCP server for TouchDesigner enabling AI agents to control and operate TouchDesigner projects via the Model Context Protocol. Requires Docker or Node.js to be installed. Environment variables for Docker setup are configured via a .env file copied from the dotenv template.
Repository-wide counts · Cached 2026-03-19
The TouchDesigner MCP MCP server is a publicly available project. Review the upstream repository for installation instructions, supported tools, compatibility, permissions, and current maintenance status.
Configuration, transport, authentication, and runtime requirements vary by project. Open the repository before connecting and use the smallest set of credentials and permissions required.
Open the TouchDesigner MCP repository to read the latest documentation.
Compare source, connection, and authentication details before choosing an implementation.
View the complete category
upstash
Context7 MCP server providing up-to-date, version-specific documentation and code examples for libraries, enabling coding agents to fetch accurate docs and code snippets. Requires an API key for higher rate limits, passed via CONTEXT7_API_KEY header.
Microsoft Corporation
A Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright. Enables LLMs to interact with web pages through structured accessibility snapshots, bypassing the need for screenshots or visually-tuned models.
feder-cr
AIHawk is an anti detect browser and web browsing agent, open source, with an MCP server for coding agents: undetected, no captchas, no blocks. It requires an OpenRouter API key for the standalone web UI mode, which can be provided via the --openrouter-key flag or the OPENROUTER_API_KEY environment variable or a .env file in the running directory.
Build-time snapshot · Retrieved 2026-10-05
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:
Tell the AI agent you already use:
That's it. The full procedure lives in the Installation Guide — it opens with a table matching each AI app to its route, and everyone starts from TouchDesigner Setup. Or follow it yourself, step by step.
If you are updating, please refer to the procedure in the Latest Release.
This server enables AI agents to perform operations in TouchDesigner using the Model Context Protocol (MCP).
Tools allow AI agents to perform actions in TouchDesigner.
| Tool Name | Description |
|---|---|
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 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. |
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. |
Prompts provide instructions for AI agents to perform specific actions in TouchDesigner.
| Prompt Name | Description |
|---|---|
Search node |
Fuzzy searches for nodes and retrieves information based on name, family, or type. |
Node connection |
Provides instructions to connect nodes within TouchDesigner. |
Check node errors |
Checks errors and warnings on a specified node, and recursively for its descendants. |
Not implemented.
Looking for local setup, client configuration, project structure, or release workflow notes? See the Developer Guide for all developer-facing documentation.
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 .tox component). Each release declares the API version it ships with (expectedApiVersion) and the minimum it supports (minApiVersion, currently 1.3.0). The connected component's API version is compared against those two values — the npm package version itself never gates compatibility, so updating the MCP server alone never invalidates a supported component.
| API Server (component) | Condition | Behavior | Status |
|---|---|---|---|
| = expected API version | Matches the shipped .tox |
✅ Works silently | Compatible |
| ≥ minimum, < expected | Older component | ⚠️ "Update Recommended" notice appended to responses, continues | Warning |
| > expected, same MAJOR | Newer component | ⚠️ Warning to update the MCP server, continues | Warning |
| MAJOR above expected | Newer API generation | ❌ Execution stops — update the MCP server | Error |
| < minimum (or missing) | Too old | ❌ Execution stops — update the component | Error |
To resolve compatibility errors:
touchdesigner-mcp-td folder and replace it with the newly extracted contents.mcp_webserver_base component from your TouchDesigner project and import the .tox from the new folder.For developers: When developing locally, run npm run version after editing package.json (or simply use npm version ...). This keeps the Python API (pyproject.toml + td/modules/utils/version.py), mcpCompatibility.expectedApiVersion, 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.
TouchDesignerClient 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.ECONNREFUSED / "connect refused": start TouchDesigner, ensure the WebServer DAT from mcp_webserver_base.tox is running, and confirm the configured port (default 9981).ETIMEDOUT / "timeout": TouchDesigner is responding slowly or the network is blocked. Restart TouchDesigner/WebServer DAT or check your network connection.ENOTFOUND / getaddrinfo: the host name is invalid. Use 127.0.0.1 unless you explicitly changed it.ILogger, so you can check the MCP logs to understand why a request stopped before hitting TouchDesigner.We welcome your contributions!
git checkout -b feature/amazing-feature).npm test).git commit -m 'Add some amazing feature').git push origin feature/amazing-feature).Please always include appropriate tests when making implementation changes.
MIT