Skip to main content
Glama
axysar

touchdesigner-agent-mcp

by axysar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to touchdesigner-agent-mcp

No user-submitted related servers found.

    Related Servers

    • TouchDesigner MCP

      8beeeaaat
      A
      license
      B
      quality
      A
      maintenance
      A 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
      478 npm
      536
      MIT

    • TD_MCP

      NairoDorian
      A
      license
      Not graded
      quality
      B
      maintenance
      A 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

    • td-mcp

      vedant1317
      A
      license
      B
      quality
      C
      maintenance
      A token-efficient MCP server for driving TouchDesigner from AI assistants, enabling building whole node networks in one call, searching CHOP channels by glob, inspecting operators compactly, and taking screenshots of TOPs.
      16
      MIT

    • td-mcp

      tai5863
      A
      license
      A
      quality
      D
      maintenance
      MCP server for controlling TouchDesigner from AI coding agents like Claude Code and Codex CLI, enabling operator manipulation, parameter control, and screenshot capture.
      12
      MIT

    • TDPilot

      dreamrec
      A
      license
      B
      quality
      B
      maintenance
      An 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.
      100
      13
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 25 tools

    Disambiguation5/5

    Each tool targets a distinct operation (e.g., create vs. delete node, connect vs. layout, viewport capture vs. pane info). Overlap is minimal and well-explained in descriptions.

    Naming Consistency5/5

    Tools follow a consistent verb_noun pattern with 'td_' prefix for common actions and 'get_td_' for queries. Exceptions like 'exec_node_method' and 'describe_td_tools' are still clear and fit the pattern.

    Tool Count4/5

    25 tools is on the higher end but justified by the breadth of TouchDesigner capabilities covered. No tool seems superfluous, though a few could potentially be combined (e.g., get_td_classes and get_td_class_details).

    Completeness5/5

    Covers the full lifecycle: create, read, update, delete nodes; parameter management; connections; cooking; layout; file I/O; scripting; and inspection. Gaps are minor (e.g., timeline control) but not essential for core automation.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources