Skip to main content
Glama
Pantani

tdmcp

by Pantani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to tdmcp

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
    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

  • TD_MCP

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

    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

  • 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
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 508 tools

Disambiguation2/5

Despite exceptionally detailed, cross-referenced descriptions, the massive number of overlapping builders creates real selection hazards: dozens of create_* visual-effect tools (feedback, depth, particle, glow variants), many connect_*/scaffold_* external-system bridges that all build similar OSC/skeleton container scaffolds, and multiple body/pose tracking tools (setup_body_tracking, create_pose_tracking, setup_mediapipe_plugin) with nearly identical purposes. An agent browsing 508 tools would frequently misfire despite the careful 'use X instead' disambiguation notes.

Naming Consistency3/5

The dominant snake_case verb_noun pattern (create_*, get_*, set_*, manage_*, connect_*) is strong, but construction actions are scattered across five near-equivalent verbs — create_*, setup_*, scaffold_*, connect_*, and build_* — all meaning 'make a network'. A few outliers (macro_recorder, one_source_five_ways, moodboard_to_system, caption_top) further break the otherwise predictable convention.

Tool Count1/5

508 tools is an extreme mismatch by any standard — more than 10x the upper bound of a well-scoped server. Even a domain as broad as TouchDesigner automation cannot justify this many entry points; the surface is far beyond what an agent can effectively navigate or what any single workflow would use.

Completeness5/5

The surface is exhaustively complete for the stated domain: node lifecycle CRUD, parameter inspection/mutation, network build/repair/optimize, audio/video analysis, output routing, packaging/recipes, vault workflows, external integrations, and performance monitoring. There are no obvious dead ends — every created network has inspection, modification, preview, and portability counterparts.

Maintenance

ActivitySlowing
ResponsivenessResponsive

Resources