ImageStep — Claude Code MCP server: generate and edit images

What ImageStep does

ImageStep hands the agent a set of image tools. generate turns a prompt into images, transform runs a single operation, run_preset executes a saved multi-step preset, job_status reports progress, search_assets finds assets, and save_preset stores a chain under a name and version. A preset with subjects keeps one character or product consistent across a batch, and slug@version pins an exact version.

Image bytes never come back into context. A tool answers with an asset id, a path to a temp file, or a URL. transform has two modes and the input decides which one runs, not the agent. Synchronous mode needs exactly one local file or one URL, a deterministic op, and wait: true — nothing lands in the account. Everything else becomes a job with progress and cancellation. A local server returns path; the hosted endpoint at https://mcp.imagestep.dev/mcp returns a signed link with expiresInSeconds.

You need an IMAGESTEP_API_KEY. Paid tools accept dry_run, which quotes the exact price and creates nothing, so a bad parameter is refused before any credit is charged. Calling a write tool again with the same idempotency_key and the same arguments returns what the first call produced instead of submitting a second job.