Import images by URL or binary upload (no base64)

[flocom]

Why

Embedding a large input image as base64 in the MCP request is too heavy. This adds two lightweight ways to send images in, mirroring the deliver:'url' output feature.

What

Image fields (screenshot.image, background.image, elements[].image) now also accept:

• appscreen-file://<id> — a reference returned by the new POST /upload endpoint, which accepts raw image bytes (no base64) and stores them in the TTL filestore. Resolved straight from memory (no HTTP round-trip), auto-deletes after ?ttl (default 3600s).
• http(s) URL — the server fetches the image.

(data URL, raw base64, and server file path still work.)

curl -X POST "https://host/upload?ttl=600" -H "Content-Type: image/png" --data-binary @shot.png
# → { "ref": "appscreen-file://ab12…", "url": "https://host/files/ab12….png", "bytes": 408200 }
# then pass "image": "appscreen-file://ab12…"

Verified

• Uploaded a 408 KB Reeflo JPG as raw binary → got a ref → rendered correctly (placed in the mockup).
• http(s) URL input: server fetched an external PNG and rendered it.

This is the recommended Mac → remote server path for large screenshots, and works through the Cloudflare Tunnel.

🤖 Generated with Claude Code