Fashio AI

Official registry Media and design

On-model and ghost-mannequin fashion photos from a product photo. Spends credits; needs an API key.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http fashio-ai 'https://mcp.fashiolabs.com/mcp' --header 'Authorization: <Bearer fio_live_... (Fashio API key). Calls spend credits.>'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "fashio-ai": {
            "type": "http",
            "url": "https://mcp.fashiolabs.com/mcp",
            "headers": {
                "Authorization": "<Bearer fio_live_... (Fashio API key). Calls spend credits.>"
            }
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. fashio-mcp
  2. Setup
  3. Tools
  4. Billing
  5. Development
  6. Links
  7. License

fashio-mcp

MCP (Model Context Protocol) server for the Fashio API — lets Claude, Cursor, and other MCP-speaking agents generate on-model fashion photos directly, as tool calls.

Fashio turns a garment or product photo into publish-ready e-commerce photography and video with AI — virtual try-on, catalog packs, background removal, upscaling, reframing, and more. This package is the official MCP client for its public v1 REST API.

It's a thin wrapper: every tool here calls the same public api.fashiolabs.com v1 REST API a curl script would. No local business logic — the API is the source of truth.

Setup

  1. Create a free API key at fashiolabs.com → Profile → API Keys.
  2. Add Fashio to your MCP client — pick one of the two options below.
Option A — Remote (hosted, no install)

mcp.fashiolabs.com runs this same server as a hosted HTTP endpoint — nothing to install, just add the URL with your key as a bearer token:

{
  "mcpServers": {
    "fashio": {
      "url": "https://mcp.fashiolabs.com/mcp",
      "headers": {
        "Authorization": "Bearer fio_live_..."
      }
    }
  }
}

(Exact config UI/field names vary by client — Claude Desktop, Claude Code and Cursor all support adding a remote/HTTP MCP server by URL with custom headers as of 2026.)

Option B — Local (this package, stdio)

Runs on your own machine instead of a hosted endpoint — same tools, same billing.

Claude Desktop / Claude Code

claude_desktop_config.json (or .mcp.json for Claude Code):

{
  "mcpServers": {
    "fashio": {
      "command": "npx",
      "args": ["-y", "fashio-mcp"],
      "env": {
        "FASHIO_API_KEY": "fio_live_..."
      }
    }
  }
}
Running from source
git clone https://github.com/fashiolabs/fashio-mcp.git
cd fashio-mcp
npm install
npm run build

Then point your client's config at the built entry point instead of npx:

{
  "mcpServers": {
    "fashio": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-server/dist/index.js"],
      "env": { "FASHIO_API_KEY": "fio_live_..." }
    }
  }
}

Tools

ToolDescription
list_modelsEvery valid toolId for create_generation, with input shape and fallback price.
list_fashion_modelsBrowse the AI person model catalog (gender, limit).
list_venuesBrowse the venue/background catalog (limit).
list_posesBrowse the pose catalog (type, limit).
upload_imageUploads a local file (jpg/png/webp, max 8MB) and returns a usable URL.
create_generationStarts a job — same request shape as POST /v1/generations. Returns {id, status: "processing"}. Pass templateSetId to reuse a saved style instead of picking fashion_model/venue/pose by hand.
get_generationPolls a job by id until status is completed or failed.
get_accountEmail, plan, diamond (credit) balance, and renewal date for the account that owns the key.
create_template_setSaves a completed generation's fashion_model/venue/pose/shotType/stylePreset/ratio as a named preset — reuse it on a new garment via create_generation's templateSetId.
list_template_setsLists presets saved with create_template_set.
delete_template_setDeletes a saved preset.
list_ready_template_setsBrowses Fashio's own curated "ready photoshoot" library (model + venue + pinned poses) — a different, larger catalogue than your own saved presets above.
get_ready_template_setFetches one curated set, including its full list of shots.
create_catalog_jobRuns your product photo through every shot (or a chosen subset) of a curated photoshoot set — one image per shot, billed per shot. Poll with get_generation.

See docs.fashiolabs.com for the full endpoint reference these tools wrap, and docs.fashiolabs.com/llms-full.txt for a plain-text version written for an LLM to read in one pass — including which images.* fields each toolId needs.

Billing

There is no separate MCP or API plan. Every create_generation call deducts diamonds (Fashio's credit unit) from the account that owns the API key — exactly as a generation from the app or dashboard would. A failed generation refunds its diamonds automatically.

Development

npm run dev    # tsc --watch
npm run build
npm start      # runs dist/index.js directly (expects FASHIO_API_KEY in env)

License

MIT — see LICENSE.

Frequently asked questions

What is Fashio AI?

On-model and ghost-mannequin fashion photos from a product photo. Spends credits; needs an API key.

How do I install Fashio AI?

It runs as a remote server. In Claude Code: claude mcp add --transport http fashio-ai 'https://mcp.fashiolabs.com/mcp' --header 'Authorization: <Bearer fio_live_... (Fashio API key). Calls spend credits.>'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Fashio AI need an API key?

Yes. It expects Authorization, which you set in its configuration.

Is Fashio AI open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Fashio AI?

It is published by fashiolabs. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.