jwmcp
Related Servers
Alternatives to jwmcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to author and edit production CAD drawings — mechanical parts, architectural plans, P&IDs, ISO-compliant dimensions, tolerances and title blocks — either live in AutoCAD through COM on Windows or headlessly via ezdxf anywhere. It also reads existing drawings back to support understanding, critique, topology checks and quantity takeoffs.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to draft, edit, read, and validate CAD drawings either by driving a live AutoCAD session over COM or headlessly through ezdxf on any platform, spanning mechanical parts, architectural plans, P&IDs, ISO-compliant dimensioning and GD&T, and quantity takeoffs into spreadsheets.-
- FlicenseNot gradedqualityAmaintenanceGives AI agents one typed tool contract for CAD automation, driving either a live Windows drafting seat through COM or a headless DXF engine anywhere. It enables mechanical part sheets, P&ID drafting and reading, architectural floor plans, ISO GD&T and dimension-tolerance validation, plus drawing understanding and takeoff workbooks.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to control CAD applications such as AutoCAD, ZWCAD, GstarCAD, and BricsCAD through natural language or direct tool calls for drawing, layer/entity/block management, data export, and file operations.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to draft, read, and validate real CAD drawings through a single typed contract that drives live AutoCAD over COM on Windows or a headless ezdxf engine anywhere, covering mechanical parts, architecture, P&IDs, and ISO GD&T/dimension standards. It also inspects existing drawings for scale, topology, and differences, and produces takeoff workbooks and plotted sheets.-
- AlicenseNot gradedqualityBmaintenanceEnables 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.1Apache 2.0
TDQS
Scored across 34 tools
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.
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.
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.
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.