Skip to main content
Glama

Related Servers

Alternatives to jwmcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with CAD software through semantic spatial topology and architectural ontology, supporting drawing, block/layer/entity management, and safe preview-apply transaction workflows for AutoCAD, ZWCAD, GstarCAD, and BricsCAD.
      1
      Apache 2.0
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to drive AutoCAD 2024+ and AutoCAD LT through live COM and AutoLISP engines, with support for headless DXF processing, ISO GD&T, P&ID drafting, and Rhino.Inside Grasshopper battery workflows.
      162
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables an AI assistant to conversationally control Autodesk AutoCAD, drawing, inspecting, and editing plans, and includes a cross-platform DXF engine that runs without AutoCAD on macOS and Linux. It exposes tools for rendering views as images, batching geometry, blocks, and structures, measuring and checking plans, and undoing whole batches.
      12
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI models such as Claude, Gemini, Cursor, and ChatGPT to directly drive CAXA CAD for automated mechanical drafting, including GB-standard drawing frames and title blocks, geometric primitives, dimension annotations, parametric part generation, and viewport screenshots. It also manages the CAXA process and window so drawings can be opened, zoomed, and exported without manual intervention.
      1
      MIT

    TDQS

    B3/5.0

    Scored across 34 tools

    Disambiguation4/5

    A clear prefix scheme separates the four subsystems: jww_* for read-only .jww inspection, drawing_* for editable drawings, scan_* for raster/vector PDF conversion, and gaihen_* for the Jw_cad bridge. Within families some tools are close (jww_preview vs drawing_preview vs gaihen_preview, drawing_import_jww vs scan_vector_import, jww_info vs drawing_info), but the descriptions explain the source object well enough to disambiguate.

    Naming Consistency5/5

    Every tool is snake_case with a namespace prefix (jww_, drawing_, scan_, gaihen_) plus an action or noun suffix, and the pattern is followed throughout. There is no mixing of camelCase, and the domain abbreviations (jww, gaihen, jwc) are used consistently.

    Tool Count3/5

    34 tools is heavy, well above the comfortable 3-15 range. The breadth (four genuine subsystems of ~8 tools each) justifies much of it, but several near-duplicate previews/imports inflate the count and it would be cleaner split into sub-servers.

    Completeness4/5

    Coverage across read (.jww), edit (drawings), convert (scans), and the Jw_cad round-trip bridge is broad and near-complete CRUD for drawings. Minor gaps remain, e.g. no delete/rename for a saved drawing and no direct .jww write-back, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues