Embody
Related Servers
Alternatives to Embody
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAn 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.10016MIT
- 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.2MIT
- AlicenseBqualityDmaintenanceA 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.16MIT
- AlicenseNot gradedqualityCmaintenanceA 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
- AlicenseNot gradedqualityDmaintenanceHigh-performance MCP server that enables AI assistants to control TouchDesigner live via WebSocket, providing 37 tools for nodes, parameters, scripting, and more.5MIT
- AlicenseAqualityDmaintenanceMCP server for controlling TouchDesigner from AI coding agents like Claude Code and Codex CLI, enabling operator manipulation, parameter control, and screenshot capture.1235 PyPIMIT
TDQS
Scored across 24 tools
Tools have largely distinct purposes: local TD lifecycle (get_td_status, launch_td, restart_td) versus Convoy remote orchestration (convoy_list_nodes, convoy_call, convoy_get_job) versus dialog handling. Minor potential confusion exists between switch_instance and convoy_select_node (both change routing) and between get_convoy_status and convoy_list_nodes, but descriptions differentiate them.
All names use snake_case, with a clear convoy_ prefix for most remote Convoy tools and no prefix for local bridge tools. Exceptions like get_convoy_status (Convoy-related but unprefixed) and convoy_owlette (noun rather than verb_noun) are minor deviations; overall the pattern is readable and consistent.
24 tools is on the heavy side for a single MCP server. While the domain (distributed TouchDesigner orchestration) justifies many operations, some niche tools such as convoy_owlette, convoy_forget_node, and convoy_ack_job could potentially be consolidated or exposed as options, placing it in the borderline 16-25 range.
Covers local TD launch/status/restart, dialog management, and extensive Convoy node/job/artifact lifecycle (list, start, restart, forget, update, call, batch, cancel, ack, get/save artifact, send file). Missing a direct local quit without relaunch and a way to discover available Envoy operations for convoy_call, but core workflows are present.