Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
MCP server for TouchDesigner - Control and operate TouchDesigner projects through AI agents
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
链接指向作者自己的文件;我们不托管也不重新打包它。打开文件后,Claude Desktop 会进行安装。
在终端中运行这条命令
claude mcp add touchdesigner -- npx -y touchdesigner-mcp-server粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"touchdesigner": {
"command": "npx",
"args": [
"-y",
"touchdesigner-mcp-server"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"touchdesigner": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"touchdesigner-mcp-server"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 8beeeaaat 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(1.2.0)于11个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js, MCPB。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Draugr
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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