hp-mcp-autocad
Related Servers
Alternatives to hp-mcp-autocad
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables Claude to control AutoCAD—draw, edit, query, layers, blocks, annotations, screenshots, plot to PDF—using plain language.812MIT
- AlicenseNot gradedqualityBmaintenanceLets Claude draw in and inspect the AutoCAD session already running on a Windows PC by attaching over COM, so no add-in or restart is needed. Provides 32 tools for drawings, layers, geometry, dimensions, blocks, queries, view capture and PDF plotting, with an edit guard, busy guard and one undo step per tool.MIT
- FlicenseNot gradedqualityDmaintenanceEnables Claude Web to control a local AutoCAD instance via MCP, exposing 149 tools for CAD operations with dual COM/ezdxf backend support.-
- AlicenseNot gradedqualityCmaintenanceEnables users to control AutoCAD, GstarCAD, or ZWCAD through natural language via Claude Desktop. It provides tools for drawing geometric shapes, adding text and dimensions, and managing CAD files using the Windows COM interface.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to connect to an already-running full AutoCAD instance through COM Automation, reading and drawing geometry live in the open drawing with 50 tools covering entities, layers, queries, modifications and AutoLISP escape hatches. Every tool call lands as a single undo step, so changes can be reversed with one Ctrl+Z.MIT
- AlicenseNot gradedqualityBmaintenanceConnects Claude Desktop to a running AutoCAD instance over local Windows COM, letting users query, draw, edit, organize layers, measure areas, take off quantities, and export sheets to PDF using plain language. Every action is undoable, logged, and optionally restricted to read-only mode with no network exposure.MIT
TDQS
Scored across 8 tools
Several operations overlap: insert_symbol(category) vs insert_valve/insert_instrument/insert_pump/insert_tank, and block.insert also places symbols; connect_equipment vs draw_process_line vs entity.create_line all draw lines; create_text vs create_mtext vs add_equipment_tag all place text. Grouping helps, but an agent must guess which layer of abstraction to use for the same visual result.
Most names follow verb_noun snake_case (create_line, insert_symbol, zoom_extents, set_current), and namespacing by group keeps bare nouns like list/get/count unambiguous. Minor deviations: bare verb operations (create, open, info, save, undo) and kebab-case in the batch examples (create-line, create-text) drift from the tool naming convention.
Eight groups is tidy, but the actual operation surface is roughly 70 commands, well past the comfortable range for one server. The domain breadth justifies much of it, yet P&ID-specific inserts duplicate generic entity/block operations and could be trimmed.
Coverage is broad: entity CRUD plus transforms, layers, blocks with attributes, dimensions/leaders, drawing file lifecycle, plotting, viewport screenshots, and a batch escape hatch. Gaps remain in modifying or deleting P&ID-specialized items (tags, line numbers, valves) and no layer delete or text-edit operation.