plug.directory
Add my server

ImageStudio_generate_and_upload

1 MCP server offers this tool

What it usually takes

  • guidance_scale – in 1 of 1
  • height – in 1 of 1
  • model_name – in 1 of 1
  • negative_prompt – in 1 of 1
  • num_inference_steps – in 1 of 1
  • prompt – in 1 of 1
  • prompt_improve_instruction – in 1 of 1
  • randomize_seed – in 1 of 1
  • seed – in 1 of 1
  • use_negative_prompt – in 1 of 1
  • width – in 1 of 1

No server marks it as only reading: treat it as able to change data.

From each publisher's own tool list. We never call a tool.

Servers

ServerInputsRead-only?
Z Image Turbo co.huggingface.nsfwalex/imagestudio Generate, then upload the result to R2 outside the GPU window. Generator yielding ``(image, seed, r2_status, progress)``. Streams per-step sampling progress (image still None) and finishes with the real image, seed and R2 status once the upload completes. The image is always the original HF-generated asset; ``r2_status`` reports the uploaded filekey, bucket and a presigned ``r2_url`` on success (or the error on failure) plus the VLM ``moderation`` result. The asset is encoded as **WebP** before upload (and the returned file is WebP too) so downstream consumers only ever see WebP. The caller's unique id (``uid`` cookie) is recorded in the object's metadata.guidance_scale,height,model_name,negative_prompt,num_inference_steps,prompt,prompt_improve_instruction,randomize_seed,seed,use_negative_prompt,widthNot stated