HermesBELARABI
العربيةSearch/CheckingSign in
AcademyDirectorySolutionsStudioProjectsComparePricing Sign in
Academy → Using HermesOfficial documentation · clear explanation

Touchdesigner Mcp — Control TouchDesigner via twozero MCP

Touchdesigner Mcp — Control TouchDesigner via twozero MCP

Developer16 minutes3 questions✓ 2026-08-09
The idea in one minute

Start with meaning, then move to detail.

This lesson explains Touchdesigner Mcp — Control TouchDesigner via twozero MCP as part of Hermes internals and extension points. You will learn what it does, when it matters, and the smallest safe test that proves it works.

If you are new

If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?

For hands-on use

For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.

For specialists

For advanced readers, inspect Skill metadata, Reference: full SKILL.md, CRITICAL RULES, then verify failure modes and version compatibility.

What do you need first?

Know Python, Git, and basic project structure before changing code.

What will you know?

A clear outcome before you read.

  • Understand Touchdesigner Mcp — Control TouchDesigner via twozero MCP without assumed prior knowledge.
  • Separate the source description from what still needs testing in your environment.
  • Read the first command and identify its inputs and outputs before copying it.
Lesson terms

Short definitions before the details.

MCP
A standard way to expose external tools, resources, and services to an agent.
Skill
An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Official page description

Control TouchDesigner via twozero MCP

Topic map

What does the source say, and in what order?

  1. 01
    Skill metadata

    Start here to understand the core idea or structure.

  2. 02
    Reference: full SKILL.md

    Read this after the foundation, then connect it to the previous step.

  3. 03
    CRITICAL RULES

    Read this after the foundation, then connect it to the previous step.

  4. 04
    Architecture

    Read this after the foundation, then connect it to the previous step.

  5. 05
    Setup (Automated)

    Read this after the foundation, then connect it to the previous step.

  6. 06
    Manual steps (one-time, cannot be automated)

    Read this after the foundation, then connect it to the previous step.

  7. 07
    Environment Notes

    Read this after the foundation, then connect it to the previous step.

  8. 08
    Workflow

    Read this after the foundation, then connect it to the previous step.

  9. 09
    Step 0: Discover (before building anything)

    Read this after the foundation, then connect it to the previous step.

  10. 10
    Step 1: Clean + Build

    Finish here to verify the result and special cases.

Examples from the official page

Copy only after you understand the effect.

Hermes Agent -> MCP (Streamable HTTP) -> twozero.tox (port 40404) -> TD Python
bash "${HERMES_HOME:-$HOME/.hermes}/skills/creative/touchdesigner-mcp/scripts/setup.sh"
nc -z 127.0.0.1 40404 && echo "twozero MCP: READY"
Try it now

Read the first command and identify its inputs and outputs before copying it.

Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.

Knowledge check

Three decisions before completion.

1. What is the source of truth when “Touchdesigner Mcp — Control TouchDesigner via twozero MCP” changes?
2. What is the best way to apply this lesson?
3. What should happen before a step can modify files or an external account?