Skip to main content
Glama
Sign In
mcp-for-clo3d

mcp-for-clo3d

by ttiimmaacc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-for-clo3d

No user-submitted related servers found.

    Related Servers

    • clo3d-mcp

      Lilbonner
      A
      license
      B
      quality
      D
      maintenance
      Enables 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.
      14
      5
      MIT

    • clo3d-mcp

      larpingvibecoder
      A
      license
      C
      quality
      C
      maintenance
      Enables an AI assistant to interact with CLO3D projects, including inspecting scenes, editing patterns, sewing, changing fabrics, simulating, taking snapshots, and saving checkpoints.
      48
      1
      MIT

    • Blender MCP VXAI

      VxASI
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language control of Blender 3D through MCP clients, allowing creation, modification, and manipulation of 3D models, animations, and scenes.
      300
      MIT

    • Marvelous Designer MCP

      Laboon2501
      A
      license
      B
      quality
      C
      maintenance
      Connects 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.
      42
      MIT

    • multiCAD-mcp

      ananyabayrak
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants like Claude for Desktop or Cursor to control supported CAD applications through MCP, supporting drawing, layer and entity management, block operations, data export, and file/session control via natural language or unified tool calls.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 104 tools

    Disambiguation3/5

    Many tools have clear, distinct purposes, but several overlapping pairs exist (e.g., sew_edges vs sew_lines, add_topstitch vs topstitch_all, and multiple export/save variants). The detailed descriptions help, but with 104 tools the chance of misselection is significant.

    Naming Consistency4/5

    Almost all tools use snake_case with a verb_noun or verb_noun_phrase pattern (e.g., get_pattern_geometry, set_fabric_color, add_internal_shape). A few exceptions like marker_report, new_project, and clo_ui_nest_all_fabrics are minor deviations but still readable.

    Tool Count1/5

    104 tools is far beyond the 50-tool threshold for extreme mismatch. Even for a complex application like CLO3D, this count is excessive and likely overwhelms both agents and users.

    Completeness5/5

    The surface covers the full CLO3D lifecycle: project management, pattern creation/editing, fabric handling, sewing, simulation, avatars, collision objects, checkpoints, dialogs, and numerous export formats. Workarounds are provided for API limitations, leaving no obvious gaps.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources