Embody

Embody is a TouchDesigner companion that externalizes operator networks into diffable/readable files and includes an embedded MCP server (“Envoy”) so AI assistants can control a live TouchDesigner session (create operators, set parameters, connect/wire ops, execute Python, export/import networks, inspect errors, etc.).

Evaluated Mar 30, 2026 (0d ago)
Homepage ↗ Repo ↗ DevTools touchdesigner mcp mcp-server ai-automation version-control devtools automation
⚙ Agent Friendliness
57
/ 100
Can an agent use this?
🔒 Security
26
/ 100
Is it safe for agents?
⚡ Reliability
48
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
90
Documentation
85
Error Messages
80
Auth Simplicity
20
Rate Limits
0

🔒 Security

TLS Enforcement
10
Auth Strength
20
Scope Granularity
10
Dep. Hygiene
35
Secret Handling
60

Envoy is documented as running on localhost (reduces exposure, but still allows local network/process access if reachable). No authentication/authorization, scopes, or secret-handling details are described. The toolset includes highly privileged actions (e.g., executing arbitrary Python and mutating the live TD session), so misuse/over-trust risks are significant. Dependency hygiene and CVE status are not assessable from the provided content.

⚡ Reliability

Uptime/SLA
0
Version Stability
75
Breaking Changes
60
Error Recovery
55
AF Security Reliability

Best When

You want LLM/agent control over a local TouchDesigner session with artifacts stored as human/diffable files.

Avoid When

You cannot trust local tooling/agents to operate on a running TD project, or you need strong network security guarantees beyond localhost defaults.

Use Cases

  • AI-assisted authoring and debugging of TouchDesigner operator networks
  • Version-control friendly TouchDesigner workflows via externalized .tox/.tdn and DAT files
  • Automated migration/reconstruction of TD networks from JSON snapshots
  • Integrating TouchDesigner with MCP-capable IDE assistants for natural-language control

Not For

  • Security-sensitive remote automation without local network controls
  • Teams that require review/merge of binary .toe diffs without externalization workflows
  • Use cases that cannot run TouchDesigner or require a headless server-only API

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: Localhost MCP (no explicit auth described) Project-generated .mcp.json for client auto-discovery
OAuth: No Scopes: No

Documentation describes starting Envoy on localhost and an .mcp.json configuration. No authentication mechanism, API keys, or scopes are mentioned in the provided README content.

Pricing

Free tier: No
Requires CC: No

No pricing information provided in the supplied content.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Envoy requires an enabled parameter and a running TouchDesigner session; a paused timeline can produce errors
  • Certain operator types (clone/replicants and some Engine COMPs) cannot be externalized/handled as expected
  • Large projects may be slow if tagging is not used selectively for externalization
  • Local MCP at a fixed port may conflict with other services if not managed (single-machine assumption implied)

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Embody.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-30.

6533
Packages Evaluated
19870
Need Evaluation
586
Need Re-evaluation
Community Powered