Skip to main content
Glama
MuriloM676

AutoCAD MCP Server

by MuriloM676

Related Servers

Alternatives to AutoCAD MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables users to control supported CAD applications through AI assistants using the Model Context Protocol, supporting drawing, layers, entities, blocks, files, exports, and natural-language automation.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables users to control CAD software like AutoCAD, GstarCAD, and ZWCAD through natural language instructions via the Model Context Protocol. It supports automated drawing of shapes, layer management, and saving designs to DWG files without manual interface interaction.
      2
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to control supported CAD applications through the Model Context Protocol, allowing drawing, layer/entity/block management, data export, and file/session operations via natural-language or direct tool calls.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to control AutoCAD, ZWCAD, GstarCAD, and BricsCAD through the Model Context Protocol, supporting drawing, layer/entity/block management, data export, file operations, and natural-language CAD task automation.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to control AutoCAD, ZWCAD, GstarCAD, and BricsCAD through the Model Context Protocol, supporting drawing, layer, entity, block, file, export, and session operations via unified tools or natural-language commands.
      -

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each top-level group targets a distinct domain (drawing, view, entity, layer, block, annotation, pid, system), so selection is mostly clear. Minor overlap exists where entity.create_mtext and annotation.create_text both create text, and pid's specialized insert_valve/instrument/pump/tank parallel generic entity creation, but descriptions keep the boundaries workable.

    Naming Consistency4/5

    Namespaces and operations use a consistent snake_case verb_noun pattern (create_line, set_current, insert_symbol, add_flow_arrow). A few bare verbs (list, count, get, copy, move, erase) deviate slightly but remain conventional and readable within their groups.

    Tool Count4/5

    Eight well-grouped top-level tools is a sensible scope for a large CAD domain, avoiding a flat blizzard of 60+ operations. The grouping is heavy (each group bundles many sub-operations), but that is a reasonable encapsulation rather than a mismatch.

    Completeness5/5

    The surface covers the full CAD lifecycle: file create/open/save/export/plot, entity CRUD with transforms and boolean-style ops, layer and block management with attributes, annotation, and a dedicated P&ID workflow. Undo/redo and system diagnostics round it out with no obvious dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues