Skip to main content
Glama
rickengineroom

touchdesigner-mcp

by rickengineroom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to touchdesigner-mcp

No user-submitted related servers found.

    Related Servers

    • td-mcp

      XTNX
      A
      license
      Not graded
      quality
      C
      maintenance
      A local MCP bridge that lets AI agents build and edit real TouchDesigner networks by creating and wiring operators, setting parameters and expressions, validating the network, and viewing rendered image previews to iterate on results.
      MIT

    • TDPilot

      dreamrec
      A
      license
      B
      quality
      C
      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
      14
      MIT

    • tdmcp

      Pantani
      A
      license
      B
      quality
      A
      maintenance
      tdmcp is an open-source (MIT) Model Context Protocol server for TouchDesigner. You describe a visual in plain language and your AI assistant builds the real node network inside TouchDesigner, checks it for errors, and shows a preview — it ships an embedded operator knowledge base so the model uses real operators instead of guessing. TypeScript codebase, runs locally.
      100
      136 npm
      45
      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

    A3.7/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool maps to a distinct action or resource: status, parameter pulsing, connectivity, DAT text, CHOP sampling, TOP capture, error retrieval, operator querying, creation, parameter setting, rig building, batch editing, and deletion. No two tools appear to do the same thing, and even similar operations like list_operators vs inspect_operator are clearly differentiated by scope.

    Naming Consistency4/5

    Most tools follow a consistent td_verb_noun pattern (e.g., td_create_operator, td_set_parameters, td_list_operators). A few deviations like td_status (noun) and td_batch (bare noun) break the pattern, and td_connect/td_disconnect omit an explicit object, but the overall scheme is predictable and understandable.

    Tool Count5/5

    With 15 tools, this server sits at the upper boundary of the ideal range, but every tool earns its place by covering a distinct aspect of TouchDesigner workflows: status, graph editing, parameter control, data reading, visualization capture, and batch operations. The count is well-scoped for the complexity of the platform.

    Completeness4/5

    The tool set covers the core lifecycle (create, delete, connect, disconnect), parameter management (set, inspect), data acquisition (CHOP, TOP), error handling, and even a high-level rig builder. Minor gaps exist around operator rename, clone, or move operations, but these can be worked around with existing tools or are outside the primary scope.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources