Skip to main content
Glama
0xZoharHuang

garment-cad-mcp

by 0xZoharHuang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to garment-cad-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • my-pi

      BoxBoxmari
      A
      license
      C
      quality
      B
      maintenance
      Local-first MCP runtime for coding agents with bounded workspace access, content-preconditioned writes, AST search, LSP navigation and diagnostics, and Git status/diff. Designed to give coding agents useful repository access without treating unrestricted shell access as the default integration boundary.
      2
      13
      2
      MIT

    • Commander Plus

      yashkhou
      F
      license
      Not graded
      quality
      C
      maintenance
      A local-first MCP control-plane core that gives AI agents persistent project context through workspace registration, reusable skill routing, and health guardians over stdio.
      2,487 npm
      -

    • uacos

      caotiensinh
      A
      license
      Not graded
      quality
      C
      maintenance
      Local-first code intelligence and safety layer for AI coding agents. MCP server exposes dependency graph, impact analysis, and AST-compressed repo context, backed by typed local memory, patch-scope safety gates, and git-independent transaction rollback.
      1
      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 10 tools

    Disambiguation4/5

    Most tools target distinct actions (create, import, open, status, search, read, commit, preview, discard, revert). However, project_open and project_status both relate to viewing project state, which could cause minor confusion, though their descriptions clarify that status refreshes state while open returns it.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., project_create, changeset_commit, revision_revert). No mixed conventions or vague verbs; the naming is highly predictable and readable.

    Tool Count5/5

    The server has 10 tools, which is well within the typical 3-15 range. Each tool serves a distinct purpose in the garment CAD workflow, and the count feels proportionate to the domain without being excessive or thin.

    Completeness4/5

    The tool surface covers core project lifecycle (create, import, open, status), changeset management (commit, discard), and revision operations (revert). Minor gaps exist such as no project deletion or listing, but the provided tools cover the primary workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources