Skip to main content
Glama
Tianshang301

TianshangCAD

by Tianshang301
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to TianshangCAD

No user-submitted related servers found.

    Related Servers

    • root-ext-cad

      graphgrow
      F
      license
      A
      quality
      B
      maintenance
      CAD-engineering MCP tool server for parametric modeling, DFM validation, mechanical calculations, and more. Enables code-CAD builds (build123d/CadQuery), model inspection, meshing, and mechanical calculators via MCP stdio.
      11
      -

    • Battenmark

      halsyourpal422
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents and software to create, edit, inspect, validate, and export CAD geometry through MCP using backend-neutral typed operations, with FreeCAD/OpenCascade as the authoritative B-rep backend and JSCAD preview.
      1
      Apache 2.0

    • lambdacad-mcp

      Psalmustrack
      A
      license
      B
      quality
      A
      maintenance
      MCP server that lets AI draw in AutoLISP-capable CAD (reference BricsCAD on Linux) via a file bridge, enabling 2D drafting, 3D solid modeling, and verification with 100 tools.
      128
      2
      Apache 2.0

    • cad-mcp

      hiromitsdm
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that exposes CAD geometry reasoning over STEP files to LLMs, allowing natural language queries about parts, assemblies, dimensions, holes, and mass properties.
      -
    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

    A4.3/5.0

    Scored across 22 tools

    Disambiguation4/5

    Each cad_* tool targets a distinct domain and the 'When not to use' sections actively separate overlapping areas like cad_file vs cad_json vs cad_gltf and cad_status vs cad_validate. A few boundaries remain blurry (cad_status metrics vs cad_validate metrics, cad_version snapshots vs cad_collab branches), but the descriptions mostly prevent misselection.

    Naming Consistency5/5

    All tools follow a consistent cad_<domain> pattern, making the surface highly predictable. This uniform prefix convention is clearer than many servers using mixed verb styles.

    Tool Count4/5

    22 tools is on the heavy side, but each maps to a distinct CAD subdomain such as file, object, layer, assembly, drawing, simulation, CAM, and collaboration. The count is justified for a full CAD server rather than padding, though it is slightly above the typical 3-15 well-scoped range.

    Completeness5/5

    The surface covers the CAD lifecycle unusually well: document/file management, geometry CRUD, layers, views, constraints, assemblies, drawings, features, simulation, CAM, glTF, plugins, validation, status, and collaboration. There are no obvious dead ends—each domain includes the key create/read/update/delete or equivalent operations needed.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources