Skip to main content
Glama

Connect ComfyUI

connect_comfyui

Bridge a running ComfyUI server into TouchDesigner using tox drop or webclient build, exposing a Null TOP for downstream output.

Instructions

Bridge a running ComfyUI server: drops the TDComfyUI .tox if installed, otherwise builds a stock webclientDAT skeleton. The container exposes a Null TOP at /out as the downstream output.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo'auto' tries tox_drop first then falls back to webclient. Force one explicitly when you know which is installed.auto
parent_pathNoCOMP that will receive the ComfyUI container./project1
nameNoContainer name; defaults to 'comfyui'.
tox_pathNoExplicit .tox path. When omitted, candidates are probed in order: olegchomp/TDComfyUI, JiSenHua/ComfyUI-TD.
server_urlNoComfyUI server base URL — host:port of `python main.py --listen`.http://127.0.0.1:8188
workflow_json_pathNoAbsolute path to a ComfyUI workflow JSON exported from the web UI (Save (API Format)). Required for webclient mode.
source_top_pathNo(webclient) TOP whose current frame is sent as the workflow input image via Syphon/Spout re-broadcast.
output_top_nameNoName of the Null TOP exposed inside the container as the downstream output.out
output_modeNoHow the generated frame is pulled back into TD. 'file_watch' reloads ComfyUI's output folder via a movieFileInTOP.syphon
output_source_nameNoSpout sender / Syphon server / NDI source name to receive on. Must match the ComfyUI side.ComfyUI
watch_folderNo(output_mode=file_watch) Folder ComfyUI writes outputs to. The movieFileInTOP cycles the newest file.
poll_interval_secondsNo(webclient) How often to poll /history for completion.
activeNoStart polling / streaming immediately. Default off so the artist can sanity-check first.
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate non-read-only and non-destructive. The description adds that the tool may drop or install a .tox file and create a container, providing behavioral context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no waste. It front-loads the main verb 'Bridge' and efficiently communicates the two main paths and output structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 13 parameters and no output schema, the description is adequate but lacks details on prerequisites (e.g., needing a running ComfyUI server) and parameter-mode dependencies, which could be more complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with parameter descriptions, so baseline is 3. The tool description adds minimal extra meaning beyond the schema, only briefly referencing mode and output behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Bridge' and the resource 'running ComfyUI server', and distinguishes from siblings like connect_daydream_cloud by specifying ComfyUI-specific actions (dropping .tox or building webclient skeleton).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context but lacks explicit when-to-use or when-not-to-use guidance. Mode selection is mentioned, but no prerequisites or alternatives from sibling list are discussed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pantani/tdmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server