Run ComfyUI workflows on RunComfy

Use RunComfy's connected MCP tools. Authenticate through the client's sign-in control when required; never ask for credentials in chat. General questions about local ComfyUI do not require account access or a cloud run.

Inspect before executing

1. Call list_deployments and select the deployment the user owns and intends to use. Use get_deployment with include_payload: true for its actual workflow graph, inputs, defaults, GPU configuration and current state; the default response omits the full payload.
2. Map the user's requested changes to the workflow's real input names and node IDs. Do not guess which node controls the prompt, seed, dimensions, steps or file input. Preserve unspecified values.
3. File handling depends on the deployment schema and submit_request contract. Follow the exposed input contract rather than assuming every ComfyUI file field accepts an arbitrary URL. Do not publish private inputs without permission.
4. Use get_balance and current deployment pricing/configuration to explain the available cost estimate. GPU startup, execution and keep-warm time may affect charges; a job timestamp alone does not establish billed runtime.
5. Present deployment ID, requested overrides, expected outputs, GPU settings and budget/stop condition. Reuse the user's existing authorization. Creating, updating or deleting a deployment changes persistent resources; do that only when requested or necessary within the agreed task.

Execute and recover