8beeeaaat/touchdesigner-mcp

MCP server for TouchDesigner

515Stars on the repository
10Mods indexed here, across every type
26d agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

8beeeaaat/touchdesigner-mcp

Skill Claude CodeCodex

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…

not rated 515 +1 26d ago A 135 tokens original MIT

prepare-release

02

8beeeaaat/touchdesigner-mcp

Skill Claude CodeCodex

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…

not rated 515 +1 26d ago A 149 tokens original MIT

release-test-audit

03

8beeeaaat/touchdesigner-mcp

Skill Claude CodeCodex

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…

not rated 515 +1 26d ago A 133 tokens original MIT

8beeeaaat/touchdesigner-mcp

Skill Claude CodeCodex

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…

not rated 515 +1 26d ago A 134 tokens original MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: