fashio-mcp
OfficialRelated Servers
Alternatives to fashio-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables MCP clients to run 600+ generative AI models from fal.ai, including image, video, audio, and text, with tools for synchronous and asynchronous execution, model catalog browsing, and schema inspection.81MIT
- AlicenseAqualityDmaintenanceLets MCP-compatible hosts like Claude and Cursor use Lunaar's AI building blocks — including sketch-to-render, virtual try-on, jewelry/glasses compositing, body measurement extraction, image-to-3D, AR viewer publishing, and upscaling — as native tools called by name from chat.146 npmMIT
- FlicenseNot gradedqualityDmaintenanceExposes Vadoo AI APIs (video generation, captions, clips, podcasts, etc.) as MCP tools for use with Claude, Cursor, and ChatGPT.-
- AlicenseNot gradedqualityFmaintenanceEnables AI image processing tools such as vectorization, background removal, upscaling, and logo generation from any MCP-compatible client like Claude Code or Cursor.9 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables any MCP-compatible agent to generate and edit images using an existing Codex/ChatGPT subscription, exposing image generation and editing as tool calls.51 npmMIT
- AlicenseAqualityAmaintenanceWraps OpenAI-compatible text-to-image APIs as MCP tools, enabling image generation directly from conversations in Claude Code, Codex, Cursor, or Claude Desktop using the user's own API key.61Apache 2.0
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.