Skip to content
Skills Library
AI & agents · Tool integration

launch

/launch

This skill should be used when the user runs /touchdesigner:launch or asks to "start TouchDesigner", "launch TD", "open TouchDesigner with the MCP component", "set up TouchDesigner from scratch", or says TouchDesigner isn't running yet — it launches the TouchDesigner application with mcp_webserver_base.tox imported and waits until the MCP connection is live. For diagnosing an already-running TouchDesigner, the setup skill applies instead.

Licence
MIT
Last repository change
12.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
2
Deprecation

No signals detected. Repository changed on 12.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

This skill should be used when the user runs /touchdesigner:launch or asks to "start TouchDesigner", "launch TD", "open TouchDesigner with the MCP component", "set up TouchDesigner from scratch", or says TouchDesigner isn't running yet — it launches the TouchDesigner application with mcp_webserver_base.tox imported and waits until the MCP connection is live. For diagnosing an already-running TouchDesigner, the setup skill applies instead.

Triggers from the description

start TouchDesignerlaunch TDopen TouchDesigner with the MCP componentset up TouchDesigner from scratch
Original author description

This skill should be used when the user runs /touchdesigner:launch or asks to "start TouchDesigner", "launch TD", "open TouchDesigner with the MCP component", "set up TouchDesigner from scratch", or says TouchDesigner isn't running yet — it launches the TouchDesigner application with mcp_webserver_base.tox imported and waits until the MCP connection is live. For diagnosing an already-running TouchDesigner, the setup skill applies instead.

How it works

  1. Client integration
  2. Workflow
  3. Failure handling
Original SKILL.md headings · 44 lines, 766 words
SKILL.md preview
---
description: This skill should be used when the user runs /touchdesigner:launch
  or asks to "start TouchDesigner", "launch TD", "open TouchDesigner with the
  MCP component", "set up TouchDesigner from scratch", or says TouchDesigner
  isn't running yet — it launches the TouchDesigner application with
  mcp_webserver_base.tox imported and waits until the MCP connection is live.
  For diagnosing an already-running TouchDesigner, the setup skill applies
  instead.
name: launch
---

## Client integration

Use the connected TouchDesigner server's tools by logical name; discover the actual client namespace instead of constructing a Claude tool prefix. Slash-command examples also work as natural-language requests for the named skill. After any network mutation, read back affected parameters, check `get_td_node_errors`, and inspect `get_top_image` for TOP output when relevant. Do not rely on a post-tool hook to remind you.

# TD Launch

Launch TouchDesigner with the `mcp_webserver_base.tox` component loaded, then wait until the MCP bridge answers. The key mechanism: opening the `.tox` file *as a document* (instead of launching the bare app) makes TouchDesigner start a new project with the component already imported — no manual drag-and-drop. On macOS, `open -a TouchDesigner <tox>` routes the document to an already-running instance as well.

## Workflow

1. **Check whether launching is even needed.** Resolve the endpoint from the active MCP configuration or session context as in the setup skill; treat `http://127.0.0.1:9981` as an assumption when neither is available. Call `get_td_info`. If it succeeds, TouchDesigner is already up with the component loaded — report the versions and stop. This makes the command idempotent. If it fails and the configured host is not a loopback host, stop here: this command can launch only a local TouchDesigner application, so ask the user to start TouchDesigner on the configured remote machine and continue with `/touchdesigner:setup` instead.

2. **Check local access.** Launching requires shell access on the machine running TouchDesigner. If this chat has only MCP tools or a cloud shell, ask the user to open TouchDesigner and import the tox locally, then continue with the setup skill. Never launch in an unrelated cloud environment.

3. **Resolve the `.tox` file, in this order:**
   a. The `tox-path` argument, if given. Verify the file exists before using it.
   b. An existing copy on disk: check common locations (`~/Downloads`, `~/Documents`, the current project directory) for `mcp_webserver_base.tox` with a quick `find`/`ls`.
   c. **Download it**: fetch `https://github.com/8beeeaaat/touchdesigner-mcp/releases/latest/download/touchdesigner-mcp-td.zip` with `curl -L` into a persistent location (e.g. `~/Documents/touchdesigner-mcp/`), unzip it there, and use the `mcp_webserver_base.tox` inside. Keep the tox where it was unzipped — it may resolve bundled resources relative to its own path, so don't move the single file out of the extracted folder.

4. **Locate the TouchDesigner application.**
   - macOS: `/Applications/TouchDesigner.app` (glob `/Applications/TouchDesigner*` — versioned installs exist).
   - Windows: run PowerShell explicitly from a Bash environment and capture the newest matching executable:
     ```bash
     powershell.exe -NoProfile -Command 'Get-ChildItem -Path "$env:ProgramFiles\Derivative" -Filter TouchDesigner.exe -Recurse -ErrorAction SilentlyContinue | Sort-Object FullName -Descending | Select-Object -First 1 -ExpandProperty FullName'
     ```
   If not found, ask where TouchDesigner is installed rather than guessing further.

5. **Launch with the tox as the opened document** (follow the active client’s shell and application-launch permissions):
   - macOS: `open -a TouchDesigner "<abs-path-to-tox>"`
   - Windows: invoke PowerShell explicitly; Bash cannot run the `start` cmd.exe built-in directly:
     ```bash
     powershell.exe -NoProfile -Command 'Start-Process -FilePath $args[0] -ArgumentList $args[1]' "<TouchDesigner.exe>" "<abs-path-to-tox>"
     ```
   If TouchDesigner is already running without the component, the same command loads the tox into the running instance on macOS; on Windows, ask the user to drag the tox into the project instead of spawning a second instance.

6. **Poll until the bridge is live.** TouchDesigner startup takes tens of seconds (longer on first run). Poll the endpoint resolved in step 1 every ~5 seconds for up to 3 minutes (run the loop in the background rather than blocking). While waiting, tell the user that a license dialog or crash-recovery prompt on the TouchDesigner side blocks startup and must be dismissed manually.

7. **Confirm end to end.** Once the port answers, call `get_td_info` and report the TouchDesigner/server versions. Note the resulting project layout: a project opened this way has no `/project1` — the component sits at the root as `/mcp_webserver_base`, and new work happens at `/` or inside a container COMP created there. If the port answers but `get_td_info` still fails, hand off to the `/touchdesigner:setup` diagnostic ladder instead of retrying blindly.

## Failure handling

If the download in step 3c fails, give the release URL and ask the user to download and unzip it manually, then re-run with the path as the argument. If the configured endpoint never answers within the timeout: the most common causes are a modal dialog in TouchDesigner (license, update, crash recovery — ask the user to look at the TD window), a mismatch between the plugin configuration and the WebServer DAT (hand off to `/touchdesigner:setup`), or the tox failing to initialize (ask the user to check TouchDesigner's Textport for Python errors and report them back). Never kill or restart a running TouchDesigner process without explicit user consent — unsaved work may be open.

Versions

RepositoryScoreLicence
This page · 8beeeaaat/touchdesigner-mcp100MIT
devdotfast/whiteboard100MIT
microsoft/vscode100MIT
lilly-logic-labs/lll-skills100MIT
workbench-soft/agent-skills100MIT
ADWilkinson/astack100MIT
terrylica/cc-skills100MIT
gn01763009/user-thoughts100MIT
Exxzzent/rocket100MIT

Database snapshot: 13.11.2026 · package version 37af109d7490 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100setup
    This skill should be used when the user runs /touchdesigner:setup or asks to verify, check, fix, or set up the TouchDesigner connection — trigger phrases include "check my TD connection", "is TouchDesigner connected", "set up touchdesigner-mcp", "TD isn't responding", "fix the…
  • 100setup
    This skill should be used when the user runs /touchdesigner:setup or asks to verify, check, fix, or set up the TouchDesigner connection — trigger phrases include "check my TD connection", "is TouchDesigner connected", "set up touchdesigner-mcp", "TD isn't responding", "fix the…
  • 100popx-touchdesigner
    Local POPX knowledge base and workflow for TouchDesigner. Use when the user mentions POPX, popsextension, POPX examples, POPX operators, or wants to build, inspect, explain, debug, or modify POPX-based setups in TouchDesigner using the bundled POPX reference corpus and live…
  • 90mcp-manage
    Use when checking capabilities or instructing the user on how to interact with specialized MCP servers like Unreal, Rhino, DaVinci, or TouchDesigner.
  • 100tdpilot-core
    Core patching discipline for TDPilot v2.4.1 — the AI assistant inside TouchDesigner. Use for all work through the td_ MCP tools: routing intent, inspecting live state, making safe edits, validating results, and recalling or learning local techniques.
  • 90pb-show-build
    Build a show across lights (grandMA3), media (Resolume) and generative visuals (TouchDesigner) from one cue list, offline first. A lane whose console or app is not running is skipped and logged while the others continue; the live rig is touched only after GO. Use for "build the…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.