Summary
Try-on becomes two calls inside the assistant instead of a web form and a wait.
The pattern is submit then read back: submit_tryon_task takes user_img_url and cloth_img_url and returns a task, query_tryon_task reads it by task_id, so several can be queued and collected in one session. Both images have to be reachable URLs — nothing here uploads a local file — and the pair is the whole surface: no catalogue, no listing of past tasks, no cancel.
What it is
A two-tool server over HeyBeauty's virtual try-on service: one call submits the task, the other reads its result.
What you get
- A try-on task submitted from a user image URL and a cloth image URL, with a cloth description and cloth id alongside
- The task fetched back by task id
Requirements
A HeyBeauty API key in HEYBEAUTY_API_KEY, and both images already hosted where the service can fetch them — the person photo and the garment are passed as URLs.
Setup effort
One command plus a key — npx -y heybeauty-mcp, then supply credentials