A
licenseB
qualityA
maintenanceA Model Context Protocol server that enables AI agents to control and operate TouchDesigner projects through creation, modification, and querying of nodes and project structures.
14
2,219 npm
547
MIT
td-atlas
by grigabyte
Related Servers
Alternatives to td-atlas
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA local-first MCP server for TouchDesigner that provides offline documentation retrieval and live control of TouchDesigner sessions, enabling AI-assisted network building and parameter management.MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to build and control TouchDesigner networks by describing visuals in natural language, with automatic node creation, verification, and preview.100129 npmMIT
- AlicenseBqualityCmaintenanceAn MCP server for TouchDesigner that lets AI agents inspect, build, wire, optimize, and stabilize live TD networks with 106 tools, plus a technique memory system for reusable patterns.10014MIT
- AlicenseAqualityDmaintenanceEnables LLMs to directly control, introspect, and build TouchDesigner networks in real-time through a Model Context Protocol server.25MIT
- AlicenseNot gradedqualityCmaintenanceEnables natural language control of TouchDesigner via AI, allowing operator creation, parameter setting, Python execution, and node graph building.7MIT
TDQS
A3.6/5.0
Scored across 46 tools
Disambiguation3/5
Most tools have distinct purposes, but several overlapping pairs exist: td_health vs td_errors, td_project_read vs td_project_text, td_snapshot vs td_variant_save, and td_project_diff vs td_variant_diff all require careful reading to pick correctly. The long descriptions help, but the sheer number of near-neighbor inspection and versioning tools creates real misselection risk.
Naming Consistency4/5
All tools share the td_ prefix, and families like timeline_run/status/cancel/profile and variant_save/list/restore/diff follow parallel patterns. However, naming mixes bare verbs (exec, render, undo, trace, build) with noun-style names (status, errors, log, scopes), and the order varies between verb_noun (set_flags) and noun_verb (project_read).
Tool Count2/5
At 46 tools, this is well past the 25+ threshold for 'too many' and approaches extreme territory. Even though TouchDesigner is a broad domain, an agent will spend significant effort just selecting among this many options, and many tools are highly specialized sub-utilities that could be consolidated.
Completeness4/5
The tool surface is remarkably comprehensive: live state inspection, error checking, editing via batch, rendering, timeline jobs, offline project read/write, versioning, scopes, annotations, palette loading, and a doctor/diagnostics tool. Minor gaps exist (e.g., no direct single-op delete outside td_build, parameter reads only via td_op_info), but the full lifecycle of inspecting, editing, verifying, and documenting a project is covered.
Maintenance
ActivityActive
ResponsivenessNo issues