Skip to main content
Glama
andyluu98

vn-autocad-claude

by andyluu98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to vn-autocad-claude

No user-submitted related servers found.

    Related Servers

    • autocad-mcp

      xstaar
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects Claude AI to AutoCAD for architectural design, enabling natural language to execute 684 commands. Automates drawing creation and editing through the Model Context Protocol.
      21 npm
      6
      MIT

    • AutoCAD MCP Server

      Ahmedmuji
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude Web to control a local AutoCAD instance via MCP, exposing 149 tools for CAD operations with dual COM/ezdxf backend support.
      -

    • AutoCAD MCP Server

      Porta048
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      3
      MIT

    • AutoCAD MCP Server

      thepiruthvirajan
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables programmatic control of AutoCAD through COM automation, allowing natural language commands to create structures, manage layers, and manipulate entities via MCP clients like Claude.
      62
      Apache 2.0

    • AutoCAD MCP

      codesknight
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients like Claude Desktop to control AutoCAD through natural language commands using the Model Context Protocol.
      2
      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

    A3.9/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each top-level tool maps to a distinct CAD domain (file, entity, layer, block, annotation, P&ID, view, system), so an agent can usually select the right one. Minor overlap exists between entity's create_mtext and annotation's create_text, and between P&ID symbol insertion and generic block insertion, but the grouped operations help differentiate intent.

    Naming Consistency4/5

    The top-level tool names are consistently single lowercase nouns, and sub-operations generally follow a readable snake_case verb_noun style. However, there are minor deviations: some verbs differ for similar actions (create_*, insert_*, add_*, draw_*), and the batch example uses kebab-case command names while descriptions use underscores.

    Tool Count5/5

    Eight domain-focused tools are well-scoped for an AutoCAD automation server. Each tool groups a set of closely related operations, keeping the MCP surface manageable while still covering a broad range of CAD functionality.

    Completeness4/5

    The set covers the full core lifecycle for drawings, entities, layers, blocks, annotations, P&ID symbols, views, and server management. Minor gaps exist, such as changing an existing entity's layer/properties, some advanced dimension types, and block explode/redefinition workflows, but execute_lisp provides an escape hatch.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources