clo3d-mcp
Related Servers
Alternatives to clo3d-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to control CLO3D for pattern creation, fabric swapping, simulation, and model export via natural language commands.50MIT
- AlicenseAqualityBmaintenanceEnables Claude to read and modify an open CLO 3D session, including drafting and sewing pattern pieces, assigning fabrics, simulating drape, capturing screenshots, exporting garments, and undoing or redoing changes.26MIT
- AlicenseBqualityDmaintenanceEnables AI-assisted garment design by letting Claude (or any MCP host) drive CLO3D — import projects, dress avatars, assign fabrics, simulate cloth, render, and export, all from a chat.145MIT
- AlicenseBqualityBmaintenanceEnables controlling CLO3D from any MCP client to inspect projects, create and edit patterns, manage fabrics and colorways, run simulations, and export models through chat.1042MIT
- AlicenseBqualityCmaintenanceConnects MCP-compatible AI agents to a local 3D garment design application through its Python API, enabling scene inspection, pattern and sewing operations, fabric/material management, simulation, mesh measurement, checkpoints, import/export, documentation search, and raw Python execution.42MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to create and manipulate 3D scenes, objects, and materials, execute Blender Python, capture visual verification views, and generate or import assets and models.MIT
TDQS
Scored across 48 tools
Most tools have clear resource/action separation (pattern_, snapshot_, avatar_, scene_, checkpoint_), but several overlapping pairs exist: clo_run_python vs clo_api_search vs clo_api_doc (all about understanding/executing CLO API), clo_status/launch/stop_bridge are distinct but 'garment_plan_preview/build/re_build' have empty descriptions, and garment_rebuild's purpose overlaps conceptually with pattern_edit_points/pattern_ops for modifying garments.
Mostly consistent 'verb_noun' snake_case (pattern_create, scene_open, avatar_list), but there are deviations: some use bare nouns (arrangement_points, scene_info, snapshot), some prefix with 'clo_' while others don't, and 'garment_plan_preview'/'garment_build' sit awkwardly next to 'clo_run_python' and 'sew'.
48 tools is heavy for an MCP server. While the domain (3D garment simulation) is broadath, the count approaches 50, which burdens agent tool-selection. Several tool families (clo_api_*, checkpoint_*, fabric_*, garment_*) could be consolidated or trimmed.
Core lifecycle is covered: scene management, pattern creation/editing, simulation, checkpoints, garment rebuilds, and avatar handling. However, notable gaps exist: no tool to delete a seam or unsew pieces, no fabric creation/management beyond listing and assignment, no animation/pose control for avatars, and garment_plan_preview/build appear to exist but have empty descriptions, leaving their capabilities unclear.