fashio-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_modelsA | Lists every valid toolId for create_generation, with its input shape and fallback diamond price. |
| list_fashion_modelsA | Browse the catalog of AI person models to use as images.fashion_model in create_generation. |
| list_venuesA | Browse the catalog of venues/backgrounds to use as images.venue in create_generation. |
| list_posesA | Browse the catalog of poses to use as |
| upload_imageA | Uploads a LOCAL image file (jpg/jpeg/png/webp, max 8MB) from this machine's filesystem and returns a URL usable in create_generation's images.* fields. |
| create_generationA | Starts an AI fashion generation job. Deducts diamonds from the account that owns the API key. Call list_models first for valid toolId values and what each needs in |
| get_generationA | Checks the status of a job started with create_generation. Poll until status is 'completed' or 'failed'. |
| get_accountA | Returns the email, plan, diamond (credit) balance, and renewal date for the account that owns this API key. |
| create_template_setA | Saves the fashion_model/venue/pose/shotType/stylePreset/ratio from a completed generation (sourceMediaId) as a named preset. Reuse it later via create_generation's templateSetId to put a NEW garment on the exact same model/venue/pose. |
| list_template_setsA | Lists every style preset saved on this account (see create_template_set). |
| delete_template_setB | Permanently deletes a saved style preset. |
| list_ready_template_setsA | Browse Fashio's own curated 'ready photoshoot' catalogue (one model + one venue + N pinned poses each) — NOT the caller's own saved presets, see list_template_sets for those. Use with create_catalog_job. |
| get_ready_template_setA | Fetches one entry from Fashio's curated photoshoot library, including its list of shots (each with an id you can pass to create_catalog_job's shotIds). |
| create_catalog_jobA | Runs your product photo(s) through every shot (or a chosen subset) of one of Fashio's curated photoshoot sets (see list_ready_template_sets), producing one image per shot. Billed per shot. Poll with get_generation — resultUrls holds every shot's output once completed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Most tools have clearly distinct purposes, but list_models vs list_fashion_models and list_template_sets vs list_ready_template_sets could cause confusion. Detailed descriptions clarify the model-catalog vs AI-toolId and saved-preset vs curated-catalog distinctions.
All tools follow a consistent verb_noun snake_case pattern, such as list_*, create_*, get_*, delete_*, and upload_*. Minor noun ambiguity like 'models' vs 'fashion_models' does not break the naming convention.
14 tools is well within the ideal range and each tool supports a distinct part of the fashion generation workflow: catalog browsing, upload, generation, account management, and template handling. No redundant tools inflate the set.
The set covers the core lifecycle: browse catalogs, upload assets, create and poll generations, manage saved template sets, and run batch catalog jobs. Minor gaps such as updating a template set or canceling a generation are not essential to the domain.