A
licenseA
qualityC
maintenanceLets Codex inspect, build, wire, tune, sample, and visually verify running TouchDesigner projects for generative visuals, audio-reactive systems, and fast agent-assisted prototyping.
15
MIT
hydra-mcp
Related Servers
Alternatives to hydra-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to generate cinematic video and image assets and perform autonomous timeline assembly, multi-track audio editing, chroma-key compositing, and local draft manipulation from conversational prompts.1MIT
- 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 gradedqualityCmaintenanceEnables an LLM to drive a live Bespoke Synth, including module graph editing, control modulation, sequencing, playback control, and audio analysis feedback with visualizations.AGPL 3.0
- AlicenseNot gradedqualityFmaintenanceEnables AI agents to programmatically control a live Excalidraw canvas through element-level CRUD operations and real-time synchronization. It allows agents to iteratively build, inspect, and refine diagrams while providing visual feedback via screenshots and scene descriptions.1,625 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables a coding agent to see and hear the host machine via webcam stills, microphone speech-to-text, and optional text-to-speech replies, all processed locally.MIT
TDQS
A4.1/5.0
Scored across 19 tools
Disambiguation4/5
Most tools map cleanly to a distinct action in the Hydra workflow, and the descriptions are unusually precise. A few close pairs exist — hydra_sketch vs hydra_load both replace the whole composition, and hydra_block vs hydra_crossfade are write operations differing only in transition — but their purposes are clearly separated in the docs.
Naming Consistency4/5
All tools share the hydra_ prefix and lowercase snake_case, which makes the set feel cohesive. However, the names mix nouns (hydra_state, hydra_document, hydra_reference) with verbs (hydra_drop, hydra_render, hydra_save), so the pattern is predictable but not a strict verb_noun convention.
Tool Count3/5
At 19 tools, the server is on the heavy side of the ideal range. The count is defensible given the broad domain — composition editing, state inspection, rendering, media sources, audio, persistence, and video output — but a few tools could plausibly be consolidated without losing clarity.
Completeness4/5
The core composition lifecycle is well covered: read, create, replace, fade, delete, panic, save, load, list, and share. Minor gaps remain, such as no direct way to delete a saved sketch, reorder blocks, or undo changes, but an agent can accomplish the main Hydra workflows without hitting dead ends.