Custom workflows, custom nodes, a custom MCP server, and a custom skills suite — the ComfyUI setup I used to make Cyd & Julie and Garage Force.
The wrapper I built around ComfyUI so Claude can drive it natively.
I wrote a Model Context Protocol server that sits in front of ComfyUI's HTTP API and exposes its capabilities as structured tools Claude can invoke. Any Claude instance — Claude Code, Claude Desktop, a Claude-in-Chrome tab — can queue jobs, list installed models, browse LoRAs, trigger workflows from disk, fetch outputs, and check progress without leaving the conversation. It turns ComfyUI from a node editor into an AI-addressable service.
When a stock ComfyUI node doesn't do what a shot needs, I write one. Custom nodes I've authored slot into workflows like any other, but embed the quirks of my specific pipelines — the Garage Force segment-and-inpaint fork, the two-pass pose enforcement path, the API wrappers for commercial video engines that didn't have official ComfyUI support yet. Because the nodes live in the same Python environment as the server, they can also call out to my MCP server or touch the VFX Dashboard database, turning ComfyUI into a bridge between creative work and production data.
The 30+ engine profiles I maintain, and the routing recommendations I apply when picking one for a shot.
Two shipping creative projects built on this setup.
Available for editing, supervising, and tool-building consulting.
Contact