Skip to main content
Glama
Lilbonner

clo3d-mcp

by Lilbonner
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to clo3d-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-for-clo3d

      ttiimmaacc
      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
      1
      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
      MIT

    • blender-mcp

      sandraschi
      A
      license
      C
      quality
      A
      maintenance
      Enables AI-powered control of Blender through natural language, allowing users to create, manipulate, and automate 3D scenes, objects, materials, animations, and more via Claude or other MCP clients.
      71
      55
      MIT
    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.3/5.0

    Scored across 14 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources