Skip to main content
Glama
lucasmaher-hash

tdmcp

by lucasmaher-hash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to tdmcp

No user-submitted related servers found.

    Related Servers

    • 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

    • 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
      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.
      2
      100
      112 npm
      43
      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

    B3.3/5.0

    Scored across 507 tools

    Disambiguation1/5

    With 507 tools, many have heavily overlapping purposes: dozens of create_*_reactive variants, create_*_bus / connect_*_bridge scaffolds for the same external systems (QLab, Resolume, OBS), and multiple raymarching/SDF/scene builders. Even detailed descriptions cannot prevent an agent from frequently picking the wrong near-duplicate tool.

    Naming Consistency4/5

    The dominant pattern is verb_noun snake_case (create_*, get_*, set_*, manage_*), which is fairly consistent. However, there are notable deviations like macro_recorder, one_source_five_ways, generative_classics_pack, and project_documentation_site, plus several interchangeable verbs (create/build/make/setup/scaffold/connect) for similar actions.

    Tool Count1/5

    507 tools is an extreme outlier, far beyond even the 50+ threshold for a 1. This makes the server overwhelming, context-heavy, and impractical for an agent to navigate. A TouchDesigner server of this scope would still be far too large at 100+ tools.

    Completeness4/5

    The tool surface is extraordinarily comprehensive, covering node CRUD, parameter lifecycle, network inspection, packaging, recipes, vault integration, external integrations, and many generative builders. Minor gaps exist (e.g., no explicit project-open/load tool, many scaffolds are non-functional stubs), but the breadth is remarkable.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources