clo3d-mcp
Related Servers
Alternatives to clo3d-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to control CLO3D for pattern creation, fabric swapping, simulation, and model export via natural language commands.46MIT
- AlicenseBqualityAmaintenanceEnables 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
- AlicenseCqualityCmaintenanceEnables an AI assistant to interact with CLO3D projects, including inspecting scenes, editing patterns, sewing, changing fabrics, simulating, taking snapshots, and saving checkpoints.481MIT
- FlicenseNot gradedqualityAmaintenanceEnables Claude to drive a 3D modeling application through natural-language prompts for scene creation, object modification, materials, lighting, animation, MoGraph, dynamics, and rendering.-
- AlicenseNot gradedqualityBmaintenanceEnables Claude and other MCP clients to control a running DAZ Studio through the DazScriptServer plugin, covering scene queries, node and morph editing, posing and multi-character interactions, camera and lighting setup, keyframe animation, renders, content library browsing, and arbitrary DazScript execution. It also lets clients generate scenes, shot sequences, and dialogue choreography from natural-language descriptions.MIT
- AlicenseAqualityBmaintenanceEnables Claude to model 3D-printable parts by running Python scripts in a headless FreeCAD instance and exporting STL/3MF/STEP files. It also lets Claude visually inspect renders, check mesh integrity and overhang printability, measure volume and estimated mass, and open results in a slicer before printing.10MIT
TDQS
Scored across 14 tools
Each tool targets a distinct operation with no overlap. For example, add_fabric imports a new fabric while assign_fabric attaches an existing fabric to a pattern piece. Similarly, clo_ping and clo_shutdown serve different roles in connection management.
Most tools follow a verb_noun pattern (e.g., add_fabric, export_zprj, set_colorway), but pattern_count uses noun_verb, and clo_ping/clo_shutdown use a clo_ prefix, introducing minor inconsistency.
With 14 tools, the server covers the major aspects of CLO interaction (file I/O, fabric, colorway, simulation, rendering, connection) without being overly granular or sparse.
The tool set covers core workflows but has notable gaps: no pattern creation/modification, no deletion of resources, and no scene inspection beyond pattern count. This limits some agent-driven tasks.