tdmcp-bridge-endpoint

To promote a TouchDesigner bridge operation from /api/exec to a REST endpoint, you create a dedicated Python route that mirrors the existing exec logic, add a Zod validator, and rewire the bridge tools to consume the new path.

Maintaining backward compatibility when moving TouchDesigner bridge routes off /api/exec requires implementing an exec fallback in the bridge tools, ensuring current behavior is preserved if the new REST endpoint is unavailable.

To test a REST API bridge endpoint without a live TouchDesigner instance, you run offline tests including py_compile for Python routes, bridge unittests, and MSW client tests to validate the integration locally.

Yes, each TouchDesigner REST route requires a TypeScript client method and a Zod envelope to enforce a single source of truth, ensure predictable errors, and validate the request and response payloads.

Yes, this approach applies to adding or updating REST routes for TouchDesigner bridge operations such as connect, logs, and node_detail, ensuring they function safely even when the exec path is disabled.

Promoting a TouchDesigner bridge endpoint to REST improves deployment safety and observability by replacing dynamic /api/exec execution with stable, validated routes that provide predictable errors and better request tracking.