Can Claude generate multiple images at once? Yes, via a tool

Yes, but only through an image tool, because Claude itself can't generate images. With Sume's generate_image tool, one call can ask for several variations of one prompt with n; in current code no model allows more than 4 per call. For a set of different pictures, such as one per scene, Claude sends one call per image without waiting between them, then waits on all the jobs together.

Claude's side comes from Anthropic's vision docs and custom connectors article; the tool side from Sume's Image API and MCP tools and gates docs and its current MCP tool descriptions. All were read on 2026-09-29. Can Claude generate images? covers connecting the tool.

How many images can one call return?

Up to 4 today. Sume's image docs allow n up to 10 per call but say per-model ceilings are lower, and in current code no catalog model lists an n range above 4. Claude reads a model's range with image-models_list. An n outside that range is refused with 400 invalid_request, not trimmed. Bulk image generation covers the same limits from your own code.

How does Claude make one image per scene?

With several calls sent together. n gives you variations of one prompt; different scenes need different prompts, so each scene is its own generate_image call. In current code, an image create answers in milliseconds with a job id, and the tool's own guidance is to fan out the whole wave, then make one jobs_wait on all the job ids and read each with jobs_result.

For three or more calls of the same shape, Claude can use script_run instead: a short JavaScript program that runs on Sume's side and calls generate_image in a loop or in parallel. It is bounded by timeout_seconds (5–55), max_calls, and max_paid_calls, and it returns the child jobs[] to wait on. Every paid create inside it still needs its own idempotency_key.

Can Claude generate unlimited images?

No. Each image is a paid generation billed to your Sume wallet, so the real limits are your balance and any cap you set, not your Claude plan. Image billing is all-or-nothing: a completed image is billed in full and a failed one is not billed.

• dry_run=true previews a call's cost without submitting it. Sume's docs suggest generation_admission_preview or dry_run before expensive bursts.
• max_spend_usd caps a call, enforced only when provided; inside script_run, max_paid_calls caps how many paid calls one script makes.
• Your Sume plan sets how many jobs run at once. The pricing page lists concurrent jobs per plan: Pro 4, Startup 8, Scale 20.

What does Claude need before it can batch images?

Three things, whether it sends one image or twenty:

• A custom connector to https://mcp.sume.com/mcp. Anthropic makes custom connectors available on every Claude plan, with Free limited to one. Sume has no official Claude connector, and its basics page says hosted MCP still works but is not the primary path today.
• Write turned on at Sume's consent page. A read-only session returns insufficient_scope for paid calls.
• Public HTTPS URLs for any reference images. Hosted MCP cannot read files from your laptop.