ComfyUI Base 2.8.1: the MCP configuration names the comfy binary

comfy-mcp is a wrapper. Its discovery and lifecycle tools shell out to comfy-cli, which it finds through
COMFY_BIN or PATH, and an MCP client is usually launched by a GUI whose PATH is not a shell's. 2.7.0 shipped
neither transport with COMFY_BIN set: the ssh form gave an absolute path to comfy-mcp and then hoped the
machine's PATH had comfy beside it.

MEASURED 2026-09-19, driving the real stdio protocol against the testbed's ComfyUI: initialize returned
protocol 2025-06-18 and 39 tools listed either way, but server_info answered "Error executing tool
server_info" without COMFY_BIN and answered properly with it (interpreter, config path, and the workspace
base_mcp had bound). The unit tests could not have found this. They assert the shape of a config, and the
shape was fine; only speaking the protocol to a running server showed the config did not work.

Over ssh the binary beside comfy-mcp is named. Over the tunnel this machine's is, when comfy can be found,
and the command says so on stderr when it cannot rather than writing a config that fails later.

---

Step one on a fresh machine:

python3 -m zipfile -e comfyui-base.zip . && bash comfyui-base/comfyui-base-script.sh