mcp · Global

autocad-mcp

Unified MCP server for AutoCAD — File IPC, COM (multi-CAD), and headless DXF backends. 22 tools, ~130+ operations. Apache 2.0.

Feature or claim this listing

Represent autocad-mcp? Send a claim for review so we can discuss listing updates. Claims do not automatically grant ownership or verification.

Data offered docs-verified: drawing file management (create, open, save, plot_pdf, purge, audit, units) · entity creation and modification (lines, polylines, arcs, hatches, copy, array, fillet, trim) · layer management · block insertion and attributes · text, dimensions and leaders · P&ID symbols and connections · xref management · layouts and viewports · read-only drawing queries and geometry measurements · QC validation checks (layer standards, orphaned entities, duplicates) · BOM and data export to Excel · NEC electrical calculations · headless DXF generation without AutoCAD
Formats llm-inferred: DXF · PDF · Excel spreadsheets · MCP stdio
Access docs-verified: Free and open source under Apache-2.0; installed locally with uv or pip. File IPC and COM backends need an installed AutoCAD-family application; the ezdxf backend needs none.

Use cases llm-inferred: Batch-generate drainage or civils layout linework with the batch drawing tools, reducing API calls · Run layer-standards and orphaned-entity QC checks on a drawing before issue · Export entity data and BOMs from drawings to Excel for quantity take-offs · Generate DXF geometry headlessly on any platform where AutoCAD is not installed
Audience llm-inferred: BIM/civils engineers · drainage engineers · CAD technicians · GIS analysts

Constraints docs-verified: File IPC and COM backends are Windows-only · File IPC needs AutoCAD LT 2024+ with the AutoLISP dispatcher loaded manually in the session · File IPC does not support multi-CAD; only the COM backend does · The ezdxf backend is headless and cannot drive a running AutoCAD instance · No test coverage, release cadence or maintenance commitments are documented

Read-only summary of the open drawing

{
  "tool": "query",
  "arguments": {
    "operation": "drawing_summary"
  }
}

Check the drawing's layers against layer naming standards

{
  "tool": "validate",
  "arguments": {
    "operation": "layer_standards"
  }
}

Export a bill of materials from the drawing

{
  "tool": "export",
  "arguments": {
    "operation": "bom"
  }
}

Auto-extracted, unverified fields: tools, install, auth. Check upstream documentation.

Tools/install/auth auto-extracted from README; quality score heuristic (stars, recency, tool count, licence).

Metadata observed 16/10/2026 · research sweep: github-search