Skip to main content
Glama
beiming183-cloud

AutoCAD MCP Server - Codex Edition

Related Servers

Alternatives to AutoCAD MCP Server - Codex Edition

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP server for AutoCAD LT automation and headless DXF generation, exposing tools for drawing, entities, layers, blocks, annotations, P&ID, and view operations via natural language.
      8
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables natural-language control of AutoCAD via file IPC or headless DXF generation, with tools for drawing, entities, layers, blocks, annotations, P&ID, views, and system operations.
      8
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Enables MCP clients to create and edit technical drawings, manage layers and geometry, process GIS/research mapping data, generate previews and layouts, and automate AutoCAD documents on Windows through COM.
      225
      61 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to connect to and automate AutoCAD on Windows via COM, exposing tools to inspect drawings and layers, create geometry and text, manage system variables, run commands, and save or open drawings. Requires full AutoCAD running with a drawing open.
      1
      MIT
    • F
      license
      B
      quality
      B
      maintenance
      FastMCP server for automating AutoCAD via COM on Windows, enabling drawing creation, entity drawing, and drawing management through natural language commands.
      46
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural-language control of AutoCAD LT for automation and headless DXF generation, supporting drawing, entity, layer, block, annotation, P&ID, and system operations via an MCP interface.
      MIT

    TDQS

    A3.6/5.0

    Scored across 12 tools

    Disambiguation4/5

    The tools are organized by domain (product, drawing, entity, layer, etc.), which gives each a distinct purpose. However, there is some overlap: product.fillet_edges and solid.fillet_edges ostensibly do the same thing, and drawing.render_preview vs view.get_screenshot both produce visual output, which could confuse an agent.

    Naming Consistency3/5

    Top-level tool names are all single nouns (product, drawing, entity, etc.), an internally consistent pattern. Sub-operation names, however, vary without a strict convention: some are verb_noun (create_line, set_properties), others are bare verbs (list, move), and some are noun phrases (capabilities, review_summary). The grouping helps, but the overall pattern is not uniform.

    Tool Count4/5

    With 12 top-level tools, each covering a distinct aspect of CAD automation, the count is well within the 3-15 ideal range. Although each tool exposes many sub-operations, the top-level granularity keeps the surface manageable and scoped appropriately for the domain.

    Completeness4/5

    The set provides broad coverage: drawing file lifecycle, entity CRUD, layers, blocks, annotations, 3D solids, P&ID symbols, transactions, view management, and system health. Some niche operations (e.g., fillet_edges) are stubbed with capability errors, and advanced selection or dimension editing might be missing, but the core workflows are represented.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues