Skip to main content
Glama
aliphi

touchdesigner-mcp

by aliphi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
td_run_pythonA

Execute Python code inside TouchDesigner. Use op() to reference operators. Examples:

  • op('/project1/container1') to get an operator

  • op('/project1').create(constantTOP, 'my_top') to create a TOP

  • op('/project1/my_top').par.colorr = 1.0 to set a parameter

  • op('/project1/my_top').nodeX = 200 to position in the network Always use full paths starting with /project1.

td_create_operatorA

Create a new operator in TouchDesigner. Operator types use TD class names like: TOPs: constantTOP, noiseTOP, compositeTOP, levelTOP, feedbackTOP, moviefileinTOP, renderTOP CHOPs: noiseCHOP, lfoCHOP, mathCHOP, filterCHOP, constantCHOP SOPs: sphereSOP, boxSOP, gridSOP, noiseSOP, transformSOP DATs: textDAT, tableDAT, scriptDAT COMPs: geometryCOMP, cameraCOMP, lightCOMP, containerCOMP

td_set_parameterA

Set a parameter on a TouchDesigner operator. Common parameter names:

  • TOPs: colorr, colorg, colorb, colora, resolutionw, resolutionh, brightness, contrast, opacity

  • SOPs: radx, rady, radz (radius), tx, ty, tz (translate), rows, cols

  • CHOPs: roughness, amp, freq, period

  • General: display, render, bypass

td_connectB

Connect the output of one operator to the input of another operator in TouchDesigner.

td_list_operatorsA

List all child operators at a given path in TouchDesigner. Useful for inspecting the current state of a network.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct operation: connecting, creating, listing, running code, and setting parameters. Even though td_run_python is versatile, it is clearly for arbitrary code execution and does not overlap with the specific purposes of the other tools.

Naming Consistency4/5

All tools share the 'td_' prefix and use snake_case, but 'td_connect' lacks an explicit object while the others follow a verb_noun pattern like 'td_create_operator' and 'td_set_parameter'. This minor deviation is consistent enough for good readability.

Tool Count5/5

With 5 tools covering creation, connection, listing, parameter setting, and code execution, the count is well-scoped for the domain. Each tool serves a clear purpose without unnecessary redundancy.

Completeness4/5

The set covers core CRUD-like operations (create, connect, list, set) and includes a Python execution tool for flexibility. However, it lacks dedicated tools for deletion or getting parameter values, which are minor gaps that can be worked around via td_run_python.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources