query_tryon_task
Query a tryon task with task id
LABSCO 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
USE CASES
01
Seeing a garment on a real person before ordering it
Submit the person's photo and the garment image as URLs, then read the task back by its id once it has been processed.
2 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
submit_tryon_task
Submit a tryon task with user image url and cloth image url
BEFORE YOU INSTALL
What to know first
Tools you get
2 tools when we connected. tryon_cloth is a prompt wrapping submit_tryon_task, and cloth:// is a resource; neither is a tool.
Requires
- npx on PATH
- HEYBEAUTY_API_KEY in your environment
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
Build from source
TERMINAL
git clone https://github.com/chatmcp/heybeauty-mcp
cd heybeauty-mcpInstall dependencies
TERMINAL
npm installBuild the server
TERMINAL
npm run buildnpx
TERMINAL
npx -y heybeauty-mcpMCP Clients
Any MCP client — npx
ANY MCP CLIENT — NPX · JSON
{
"mcpServers": {
"heybeauty-mcp": {
"command": "npx",
"args": [
"-y",
"heybeauty-mcp"
],
"env": {
"HEYBEAUTY_API_KEY": "<YOUR_HEYBEAUTY_API_KEY>"
}
}
}
}Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"heybeauty-mcp": {
"command": "node",
"args": [
"<YOUR_PATH_TO_HEYBEAUTY_MCP>/build/index.js"
],
"env": {
"HEYBEAUTY_API_KEY": "<YOUR_HEYBEAUTY_API_KEY>"
}
}
}
}
