No user-submitted related servers found.
Scored across 114 tools
Many tools have overlapping purposes, especially in the areas of frame capture (td_screenshot, td_capture_frame, td_capture_and_analyze) and knowledge/memory (td_knowledge_recall vs td_memory_recall). The presence of legacy tools (td_patch_*, td_plan_patch) alongside their modern counterparts (td_brain_*) creates ambiguity, even though descriptions deprecate the old ones. Agents may struggle to select the correct tool among similar options.
Most tools use a 'td_verb_noun' pattern (e.g., td_get_release_delta, td_create_node). However, there are inconsistencies: some use noun_verb (td_plan_patch) vs verb_noun (td_patch_plan), and a few use different forms (td_cockpit_render, td_exec_python). The convention is mostly consistent but has notable exceptions that break the pattern.
114 tools is an extremely large number for an MCP server. While TouchDesigner is complex, many tools are redundant (legacy vs modern) or very narrow in scope (e.g., td_logger_status, td_tdresources_inspect). The set feels bloated and could be streamlined. A well-scoped set for this domain would likely be 15-30 tools.
The server covers a wide range of TouchDesigner operations: node creation/editing, parameter management, patching (both legacy and brain), knowledge/memory, monitoring, snapshots, scripting, and more. Major lifecycle operations are present. Minor gaps exist (e.g., some advanced node types or deeper introspection), but the surface is largely complete for typical workflows. The legacy tools are deprecated but still functional, adding clutter rather than gaps.