Fashio MCP Server

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

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)

Links

• fashiolabs.com — product
• docs.fashiolabs.com — full API reference
• fashiolabs.com/mcp — MCP setup guide
• fashiolabs.com/pricing — plans & credit packs

License

MIT — see LICENSE.