Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server for TouchDesigner - Control and operate TouchDesigner projects through AI agents
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
claude mcp add touchdesigner -- npx -y touchdesigner-mcp-serverPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"touchdesigner": {
"command": "npx",
"args": [
"-y",
"touchdesigner-mcp-server"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"touchdesigner": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"touchdesigner-mcp-server"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account 8beeeaaat, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.2.0) reached the registry 11 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, MCPB on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Zendesk
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Zendesk MCP Pack — tickets, users, organizations via OAuth.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
This is an implementation of an MCP (Model Context Protocol) server for TouchDesigner. Its goal is to enable AI agents to control and operate TouchDesigner projects.
English / 日本語
TouchDesigner MCP acts as a bridge between AI models and the TouchDesigner WebServer DAT, enabling AI agents to:
Tell the AI agent you already use:
Set up https://github.com/8beeeaaat/touchdesigner-mcp
That's it. The full procedure lives in the [Installation Guide](docs/installation.md) — it opens with a table matching each AI app to its route, and everyone starts from *TouchDesigner Setup*. Or follow it yourself, step by step.
If you are updating, please refer to the procedure in the [Latest Release](https://github.com/8beeeaaat/touchdesigner-mcp/releases/latest#for-updates-from-previous-versions).
This server enables AI agents to perform operations in TouchDesigner using the Model Context Protocol (MCP).
Tools allow AI agents to perform actions in TouchDesigner.
| Tool Name | Description |
|---|---|
create_td_node | Creates a new node. |
delete_td_node | Deletes an existing node. |
describe_td_tools | Generates a manifest of the available TouchDesigner tools. |
exec_node_method | Calls a Python method on a node. |
execute_python_script | Executes an arbitrary Python script in TouchDesigner. |
get_td_class_details | Gets details of a TouchDesigner Python class or module. |
get_td_classes | Gets a list of TouchDesigner Python classes. |
get_td_info | Gets information about the TouchDesigner server environment. |
get_td_module_help | Gets Python help() documentation for TouchDesigner modules/classes. |
get_td_node_errors | Checks errors and warnings on a node and its descendants. Missing files, dangling references and shader failures are warnings, so no errors does not mean healthy. |
get_td_node_parameters | Gets the parameters of a specific node. |
get_td_nodes | Gets nodes under a parent path, with optional filtering. |
get_top_image | Captures the current output of a TOP node as an image. |
update_td_node_parameters | Updates the parameters of a specific node. |
Prompts provide instructions for AI agents to perform specific actions in TouchDesigner.
| Prompt Name | Description |
|---|---|
Search node | Fuzzy searches for nodes and retrieves information based on name, family, or type. |
Node connection | Provides instructions to connect nodes within TouchDesigner. |
Check node errors | Checks errors and warnings on a specified node, and recursively for its descendants. |
Not implemented.
Looking for local setup, client configuration, project structure, or release workflow notes? See the [Developer Guide](docs/development.md) for all developer-facing documentation.
The MCP server and the TouchDesigner component are versioned on two independent axes: the npm package version and the API version (the contract between the MCP server and the .tox component). Each release declares the API version it ships with (expectedApiVersion) and the minimum it supports (minApiVersion, currently 1.3.0). The connected component's API version is compared against those two values — the npm package version itself never gates compatibility, so updating the MCP server alone never invalidates a supported component.
| API Server (component) | Condition | Behavior | Status |
|---|---|---|---|
| = expected API version | Matches the shipped .tox | ✅ Works silently | Compatible |
| ≥ minimum, < expected | Older component | ⚠️ "Update Recommended" notice appended to responses, continues | Warning |
| > expected, same MAJOR | Newer component | ⚠️ Warning to update the MCP server, continues | Warning |
| MAJOR above expected | Newer API generation | ❌ Execution stops — update the MCP server | Error |
| < minimum (or missing) | Too old | ❌ Execution stops — update the component | Error |
touchdesigner-mcp-td folder and replace it with the newly extracted contents.mcp_webserver_base component from your TouchDesigner project and import the .tox from the new folder.npm run version after editing package.json (or simply use npm version ...). This keeps the Python API (pyproject.toml + td/modules/utils/version.py), mcpCompatibility.expectedApiVersion, MCP bundle manifest, and registry metadata in sync so that the runtime compatibility check succeeds.For a deeper look at how the MCP server enforces these rules, see Version Compatibility Verification.
TouchDesignerClient caches failed connection checks for 60 seconds. Subsequent tool calls reuse the cached error to avoid spamming TouchDesigner and automatically retry after the TTL expires.ECONNREFUSED / "connect refused": start TouchDesigner, ensure the WebServer DAT from mcp_webserver_base.tox is running, and confirm the configured port (default 9981).ETIMEDOUT / "timeout": TouchDesigner is responding slowly or the network is blocked. Restart TouchDesigner/WebServer DAT or check your network connection.ENOTFOUND / getaddrinfo: the host name is invalid. Use 127.0.0.1 unless you explicitly changed it.ILogger, so you can check the MCP logs to understand why a request stopped before hitting TouchDesigner.We welcome your contributions!
git checkout -b feature/amazing-feature).npm test).git commit -m 'Add some amazing feature').git push origin feature/amazing-feature).Please always include appropriate tests when making implementation changes.
MIT