Wearo Virtual Try-On
by wearo-ioco.huggingface.wearo-io/virtual-try-on
Virtual try-on: any garment on any person, in one click
- Remote endpoint
- 2 tools
Uptime
Checked · every day
100%from 4 days of checks
Up without downtime on 4 of 4 days with data.
- No downtime
- Degraded
- Down over 5 minutes
- No data
- Not checked yet
Response time
Median 1312 ms, slowest 5% 1895 ms for the handshake and the tool list, over 30 days.
How far each check got
- Reached the address 100%
- Completed the handshake 100%
- Listed its tools 100%
2 tools at the last answer.
Every day
| Day | Result | Checks | Median |
|---|---|---|---|
| 3 Nov (today) | No downtime | 1 | 1698 ms |
| 2 Nov | No downtime | 1of 1 | 1413 ms |
| 1 Nov | No downtime | 1of 1 | 1093 ms |
| 31 Oct | No downtime | 1 | 1760 ms |
A failure counts as down time only when a second check five minutes later fails too. How we check
Connect to the publisher's own endpoint
Paste into Settings › Connectors › Add custom connector:
https://wearo-io-virtual-try-on.hf.space/gradio_api/mcp/sse Run in a terminal:
claude mcp add --transport sse virtual-try-on https://wearo-io-virtual-try-on.hf.space/gradio_api/mcp/sse Add to ~/.cursor/mcp.json:
Add to ~/.config/devin/mcp_config.json:
Add to mcp.json (Program › Install › Edit mcp.json):
Add to ~/.gemini/settings.json:
Add to config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows):
Add to ~/.config/eca/config.json (global) or .eca/config.json in the project:
{
"mcpServers": {
"virtual-try-on": {
"url": "https://wearo-io-virtual-try-on.hf.space/gradio_api/mcp/sse"
}
}
} Add to .vscode/mcp.json:
{
"servers": {
"virtual-try-on": {
"type": "sse",
"url": "https://wearo-io-virtual-try-on.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.config/zed/settings.json:
{
"context_servers": {
"virtual-try-on": {
"url": "https://wearo-io-virtual-try-on.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
Add to anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
Add to Augment Settings Panel – MCP section – Import from JSON (VS Code extension):
{
"mcpServers": {
"virtual-try-on": {
"type": "sse",
"url": "https://wearo-io-virtual-try-on.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.continue/config.yaml:
mcpServers:
- name: "virtual-try-on"
type: sse
url: "https://wearo-io-virtual-try-on.hf.space/gradio_api/mcp/sse" Add to ~/.config/goose/config.yaml:
extensions:
"virtual-try-on":
type: streamable_http
name: "virtual-try-on"
enabled: true
uri: "https://wearo-io-virtual-try-on.hf.space/gradio_api/mcp/sse"
headers: {}
env_keys: []
envs: {}
timeout: 300 This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Run in a terminal:
codex mcp add virtual-try-on --url https://wearo-io-virtual-try-on.hf.space/gradio_api/mcp/sse This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.llm/config.json:
Add to resources/assets/config/mcp.json in the installed app:
Add to ~/.boltai/mcp.json:
Add to ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
{
"mcpServers": {
"virtual-try-on": {
"url": "https://wearo-io-virtual-try-on.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/agenvoy/mcp.json:
{
"servers": {
"virtual-try-on": {
"url": "https://wearo-io-virtual-try-on.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
{
"amp.mcpServers": {
"virtual-try-on": {
"url": "https://wearo-io-virtual-try-on.hf.space/gradio_api/mcp/sse"
}
}
} For agents: the install prompt
Every step above as one Markdown text, for an assistant installing it for you.
# Install the MCP server Wearo Virtual Try-On (`co.huggingface.wearo-io/virtual-try-on`)
Its page: https://plug.directory/servers/co.huggingface.wearo-io/virtual-try-on
It runs on the publisher's servers; the client connects to its URL.
Use the section for the person's client.
## Claude Desktop
Paste into Settings › Connectors › Add custom connector:
```text
https://wearo-io-virtual-try-on.hf.space/gradio_api/mcp/sse
```
## Claude Code
Run in a terminal:
```sh
claude mcp add --transport sse virtual-try-on https://wearo-io-virtual-try-on.hf.space/gradio_api/mcp/sse
```
## Cursor, Devin Desktop, LM Studio, Gemini CLI, oterm, ECA
Merge into the place for the person's client:
- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- Gemini CLI: ~/.gemini/settings.json
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
```json
{
"mcpServers": {
"virtual-try-on": {
"url": "https://wearo-io-virtual-try-on.hf.space/gradio_api/mcp/sse"
}
}
}
```
## VS Code
Merge into .vscode/mcp.json:
```json
{
"servers": {
"virtual-try-on": {
"type": "sse",
"url": "https://wearo-io-virtual-try-on.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Zed
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Cline, AnythingLLM, Augment Code
Merge into the place for the person's client:
- Cline: cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers)
- AnythingLLM: anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory
- Augment Code: Augment Settings Panel – MCP section – Import from JSON (VS Code extension)
```json
{
"mcpServers": {
"virtual-try-on": {
"type": "sse",
"url": "https://wearo-io-virtual-try-on.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Continue
Merge into ~/.continue/config.yaml:
```yaml
mcpServers:
- name: "virtual-try-on"
type: sse
url: "https://wearo-io-virtual-try-on.hf.space/gradio_api/mcp/sse"
```
## Goose
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Codex
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## mcp-client-cli, TUUI, BoltAI, Bob Shell, Kiro, Kiro CLI
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Agenvoy
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Amp
Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
```json
{
"amp.mcpServers": {
"virtual-try-on": {
"url": "https://wearo-io-virtual-try-on.hf.space/gradio_api/mcp/sse"
}
}
}
```
Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.
Tools 2
virtual_try_on_dress_personDress a person in a garment with Wearo's virtual try-on engine. Takes a photo of a person and a photo of a garment, and returns a new image of that person wearing that garment. One generation takes from a few seconds to about two minutes. Daily limits apply per visitor. If a user passes a file as an input, use the upload_file_to_gradio tool, if present, to upload the file to the gradio app and create a Gradio File Input. Then use the returned path as the input to the tool. Returns: The generated image: the person from person_image wearing the garment from garment_image.virtual_try_on_dress_person_wedding_dressDress a person in a wedding dress with Wearo's wedding-dress mode, which renders the dress's train. Use this tool for wedding dresses, with or without a train; for any other garment use the standard try-on tool of this server. Takes a photo of a person and a photo of a wedding dress, and returns a new image of that person wearing that dress, train included. One generation takes from a few seconds to about two minutes. It counts as two try-ons against the daily limits. When the train could not be rendered, the try-on is refunded: the image is still returned, and the note says so. If a user passes a file as an input, use the upload_file_to_gradio tool, if present, to upload the file to the gradio app and create a Gradio File Input. Then use the returned path as the input to the tool. Returns: The generated image of the person wearing the dress, and a short note in English and French saying whether the train was rendered or the try-on was refunded.
From Hugging Face Spaces. Report a problem