Owns the touchdesigner-mcp release from an unreleased diff to an opened development → main release PR. Use when the user asks to "release", "cut a release", "prepare vX.Y.Z", or "ship the pending changes". Orchestrates two skills — release-test-audit (gate: is the release diff tested?) then prepare-release…
Ensure MCP-server / API changes in the touchdesigner-mcp repo ship with integration-test coverage. Use when you modify the MCP server, tool definitions/handlers, the OpenAPI schema, the TD HTTP client, the transport layer, or the TD-side Python API (src/api, src/features/tools, src/server, src/tdClient, src/transport…
Prepare a new touchdesigner-mcp release: inspect the unreleased diff since the last tag, decide independently how the MCP package version and the MCP API version each move (the API axis stays put unless the server/API contract changed), write the CHANGELOG entry, bump the six version-bearing files, commit, and open…
Audit whether the unreleased touchdesigner-mcp diff (since the last tag) is adequately covered by integration tests before a release is cut. Walks every API/MCP surface change in the release range, maps each to the integration suite that should cover it, and reports covered / gap / waived per change. Use before…
A generic workflow for self-starting TouchDesigner via computer-use (or an already-running instance), loading mcpwebserverbase.tox, and verifying any TD-side Python change (td/modules/) directly from the Textport — reading back real TD runtime values and reconciling them. Use after changing TD-side code in the…
Instructions for 8beeeaaat/touchdesigner-mcp, covering claude.md, development commands, building and development, code generation workflow and testing and quality.
MCP server for TouchDesigner - Control and operate TouchDesigner projects through AI agents. Runs locally from the touchdesigner-mcp-server npm package.