Generate videos with RunComfy

Use the connected RunComfy MCP tools; tool names may have a client-specific prefix. If authentication is needed, use the client's RunComfy sign-in flow. Keep credentials out of chat and files.

Plan the shot

1. Reuse the user's subject, action, camera motion, duration, aspect ratio, resolution, audio preference and budget. Clarify only the details needed to choose a valid request.
2. Search list_models by the requested family and capability. RunComfy includes Seedance 2.5, Wan 3.0 and LTX 2.5, as well as Kling models; current availability comes from the returned model list. Use list_model_categories when needed.
3. Call get_model for the exact returned model_id. Distinguish text-to-video, image-to-video, reference-to-video, first/last-frame and editing endpoints. Do not infer supported inputs from a family name.
4. Read the exact required input names and limits. Match duration, resolution, aspect ratio, audio and seed to the schema. A pricing tier label may differ from the encoded output dimensions.
5. Check get_balance. Show the complete request and available price estimate, including per-second pricing when applicable. Use existing user authorization and spending limits; obtain missing authorization before paid submission or publication of private input assets.

Submit once and monitor