Generate and edit images with RunComfy

Use the connected RunComfy MCP tools. The client may prefix tool names with the plugin/server name. If disconnected, direct the user to the client's RunComfy authentication control. Never request an API token in chat or add one to a file.

Choose and review

1. Establish the subject, intended use, dimensions, number of images and any reference images. Reuse details already provided.
2. Use list_models with a targeted search and category such as text-to-image or image-to-image. Use list_model_categories if unsure of a category. Start with a small page and paginate when needed.
3. Match the user's requested model family. Examples available through RunComfy include FLUX 2, Seedream 5.0 and Nano Banana 2. Use the actual returned model_id; do not construct version strings or assume a similarly named endpoint supports edits.
4. Call get_model for the selected ID. Read current input schema, required inputs, enums, defaults, pricing unit and output type. Do not reuse another model's field names or hard-code remembered prices.
5. Check get_balance before paid work. Present the model, final prompt, reference inputs, dimensions/count and available cost estimate. Proceed within the user's existing authorization and spending limit; ask only when scope or cost is missing or changed. Explain when pricing is an estimate.

Run and retrieve