Skip to main content
Glama

Related Servers

Alternatives to mech-cad-design-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to convert natural language engineering prompts into editable parametric CAD models with deterministic parsing, validation, and edit support.
      5
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to safely generate parametric CAD parts (STEP/STL) using verified templates and FreeCAD, with validation and assembly support.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables LLM agents (and humans at a terminal) to drive FreeCAD through 280+ structured tools for parametric mechanical design, drawings, FEM/CFD and other simulations, and manufacturing checks. Also supports multi-agent orchestration, letting a team of agents split one product into components, build them in parallel, and merge them back together with fitting joints.
      2
      286
      125 PyPI
      6
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agent-assisted CAD engineering, allowing users to create, validate, and export CAD designs through natural language, with a deterministic engine that has zero LLM runtime dependency.
      Academic Free v1.1
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables engineering agents to perform parametric CAD operations through a controlled MCP gateway built on FreeCAD, with transactions, diagnostics, and reproducible verification.
      2
      GNU Lesser General Public v2.1 only

    TDQS

    B3.2/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct action or resource: readiness checks, lifecycle management, knowledge retrieval, evidence recording, gear sizing, and standard-part management are clearly separated. Even closely related tools like design_confirm and design_lesson_decide have non-overlapping responsibilities (model confirmation vs. lesson publication).

    Naming Consistency4/5

    All tools follow a consistent domain prefix (design_ or standard_part_), but the suffix pattern mixes verb-first (design_start, design_confirm) with noun-first (design_status, design_mistakes) forms. The readability is high and the prefix convention provides strong predictability, so the minor deviations are not confusing.

    Tool Count5/5

    13 tools is well within the ideal 3-15 range and matches the server's broad but focused scope—covering design workflow, knowledge, validation, and standard-part integration. Each tool offers a distinct function and none feel redundant or extraneous.

    Completeness4/5

    The tool surface covers the core design lifecycle (start, status, list, confirm, record, mistakes) and standard-part management (providers, sources, register). Minor gaps exist, such as no explicit design update/delete or a standard-part search/download tool, but the existing tools allow agents to work around these via design_start/confirm and the provider/source inspection tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues