Skip to main content
Glama
Laboon2501

Marvelous Designer MCP

by Laboon2501

Related Servers

Alternatives to Marvelous Designer MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Connects MCP-capable agents to Blender and OpenSCAD for AI-driven 3D modeling, with tools and rules optimized for FDM-printable geometry.
      29
      72 PyPI
      2
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to create, inspect, validate, and modify parametric 3D models in a real FreeCAD instance through explicit MCP tools and a local bridge.
      14
      1
      GPL 3.0
    • A
      license
      A
      quality
      C
      maintenance
      Connects MCP-aware AI clients to a live SketchUp session so users can create and modify 3D models, apply materials, perform booleans and joinery, and export scenes through natural-language prompts.
      22
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects MCP-compatible clients to a live Blender scene for AI-assisted 3D workflows, enabling inspection and controlled operations on objects, materials, cameras, lights, render settings, animation, UVs, Geometry Nodes, imports, exports, and Python execution.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables LLM agents to build and modify parametric 3D models in Autodesk Fusion 360 through sketches, solid features, construction geometry, inspection tools, and in-Fusion Python execution. It connects MCP clients to a local Fusion add-in with status checks, error reporting, and unit-aware operations.
      154
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Enables controlling CLO3D from any MCP client to inspect projects, create and edit patterns, manage fabrics and colorways, run simulations, and export models through chat.
      104
      2
      MIT

    TDQS

    B3.4/5.0

    Scored across 42 tools

    Disambiguation2/5

    Several tools have overlapping purposes: save_project/export_project both save ZPRJ files with explicit paths, and list_patterns/get_pattern_info/get_pattern_points/get_pattern_topology all expose pattern geometry reads. The descriptions try to differentiate but the boundaries are subtle, which will cause misselection.

    Naming Consistency3/5

    Names are consistently snake_case and mostly verb_noun, but read operations mix list/get/inspect/info (list_patterns, get_pattern_info, inspect_sewing, pattern_arrangement) and a few are bare nouns (ping, md_api, fabric_material). This is readable but not fully predictable.

    Tool Count2/5

    42 tools is well into the 'too many' range for a single application server; many are highly specialized (pattern_arrangement, fabric_material, get_simulation_metrics) and several overlap. The set could be consolidated to ~20-25 tools without losing capability.

    Completeness4/5

    The surface covers the core domain well: pattern CRUD (create/read/move/delete), sewing create/read, fabric assignment, simulation, project import/export/checkpoint, plus docs and Python execution. Minor gaps exist (no sewing update/delete, no pattern update beyond point moves) but agents can work around them.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues