Skip to main content
Glama
U-C4N

AutoCAD MCP Pro

by U-C4N
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to AutoCAD MCP Pro

No user-submitted related servers found.

    Related Servers

    • AutoCAD MCP Server

      gpt2nndk
      A
      license
      A
      quality
      C
      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

    • AutoCAD MCP Ultra

      CaeliaEve
      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

    • AutoCAD MCP Server

      MuriloM676
      A
      license
      A
      quality
      C
      maintenance
      Enables natural-language automation of AutoCAD for drawing, editing, annotating, and exporting, as well as headless DXF generation without AutoCAD, through Model Context Protocol.
      8
      MIT

    • multiCAD-mcp

      AnCode666
      A
      license
      Not graded
      quality
      D
      maintenance
      Controls CAD applications (AutoCAD, ZWCAD, etc.) via AI assistants through the Model Context Protocol, enabling drawing, layer management, and automation through natural language or direct tool calls.
      121
      Apache 2.0

    • autocad-com-mcp

      ey2h
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI clients to control a running AutoCAD via Windows COM, supporting zoom, selection, highlighting, entity queries, and command or LISP execution without restarting AutoCAD.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 242 tools

    Disambiguation3/5

    With 242 tools, many share domains and some explicitly overlap (e.g., block_insert vs entity_create_block_ref, drawing_save vs drawing_save_as vs drawing_export_dwg). While descriptions are thorough, the sheer volume makes misselection likely, though most tools are conceptually distinct.

    Naming Consistency3/5

    Tool names are predominantly snake_case with domain prefixes (entity_, layer_, drawing_), but verb placement varies (entity_create_line vs layer_unlock) and a few lack a domain prefix (cad_batch, point_from_snap). Still readable, but not fully consistent.

    Tool Count1/5

    242 tools is an extreme mismatch for any server's purpose; even a comprehensive CAD suite would rarely need this many. This forces agents to navigate an unwieldy surface and increases cognitive load.

    Completeness4/5

    The surface is remarkably comprehensive across entity types, layers, blocks, dimensions, layouts, and specialized domains (mechanical, architectural, P&ID), with few obvious gaps. Minor gaps exist (e.g., layer rename) but are workaround-able.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week

    Resources