touchdesigner-mcp-server
Provides a pure stdio-based Model Context Protocol (MCP) server that surfaces TouchDesigner operator documentation, tutorials, version compatibility data, experimental technique writeups/snippets, and TouchDesigner Python API references as callable MCP tools (e.g., get_operator, search_python_api, get_version_info). Designed for local use (documentation served from local JSON files).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
The server is described as local/stdio-based and serves documentation from local JSON without network requests, which reduces exposure to remote data exfiltration via HTTP. However, authentication/authorization and transport security controls are not described (no auth, no TLS since it’s stdio), so access control depends entirely on the local environment and the MCP host application. Dependency hygiene appears reasonable from the small dependency list shown (no claims about CVEs).
⚡ Reliability
Best When
You want an LLM-driven coding assistant to reliably look up TouchDesigner operators/APIs and version differences while generating Python/textport guidance locally on the developer machine.
Avoid When
You need strong centralized security controls (service-to-service auth, IP allowlisting, audit trails) for remote access, or you require clear rate-limit semantics (since this appears local/stdio-based).
Use Cases
- • Ask an AI assistant for TouchDesigner operator details (parameters, tips, examples)
- • Search operators and Python API methods by query and TouchDesigner version compatibility
- • Generate/plan TouchDesigner networks by retrieving operator wiring guidance and workflow patterns
- • Learn TouchDesigner via in-tool tutorials and technique knowledge base
- • Find version-specific Python API timelines and release highlights for older/newer TD versions
Not For
- • Replacing official TouchDesigner documentation for authoritative scripting support
- • Running in restricted environments that block stdio-based MCP processes
- • Production-grade remote automation where tool traffic must be authenticated and access-controlled at the network layer
- • Real-time control loops directly via this MCP server (it’s documentation/search oriented, not a runtime TD control plane)
Interface
Authentication
No authentication mechanism is described; the server is stated as a local stdio-based MCP implementation intended for use by an MCP client (e.g., VS Code/Codium).
Pricing
No pricing information provided in the provided README/manifest content (appears to be an npm package).
Agent Metadata
Known Gotchas
- ⚠ Agents may forget to use the MCP tools and instead rely on model priors (the README explicitly mentions this as a current challenge).
- ⚠ Version mismatch risk: tool calls include version filtering/compatibility, but agents must request the appropriate TD version to avoid outdated details.
- ⚠ Search result limits: some tools default to a limit (e.g., search_operators default 10, max 50); agents may need to adjust limit for broader recall.
- ⚠ If the MCP client (VS Code/Codium integration) is misconfigured, tools may not be discovered—setup instructions reference npx/command args.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for touchdesigner-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.