Skip to main content
Glama
sebastiankoukoui

open-mcp-cad

by sebastiankoukoui
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to open-mcp-cad

No user-submitted related servers found.

    Related Servers

    • Civil 3D MCP Server

      nezolder
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to write and execute C# code directly inside Autodesk Civil 3D, using read-only and write tools plus reusable skill templates for drawing and civil object tasks.
      3
      1
      MIT

    • revit-bridge

      revitbridge
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to execute designer-confirmed code and reusable capability packs inside a running Autodesk Revit instance.
      5
      MIT

    • revit-mcp

      Mohamed-Elnahla
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with Autodesk Revit to query project data, manage elements, and execute generated code via the Model Context Protocol. It provides full compatibility with GitHub Copilot and Claude to automate BIM modeling workflows.
      13
      123 npm
      MIT

    • Civil 3D MCP Server

      DaniGhosy
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to interact with Autodesk Civil 3D through natural language, supporting tools for surfaces, alignments, profiles, corridors, pipe networks, COGO points, and AutoCAD geometry.
      9
      3
      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

    A4.3/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: document info, code execution, connection status, note reporting/clearing, message retrieval, drawing toggle, API help, examples, details, session storage, and file bootstrap operations. There is no functional overlap or ambiguity between any pair.

    Naming Consistency5/5

    All 15 tools follow a consistent verb_noun snake_case pattern (e.g., get_document_info, execute_cadwork_command, clear_check_notes, set_fast_draw). Verbs are clear and descriptive, and the naming convention is uniform throughout.

    Tool Count5/5

    The 15 tools are well-scoped for the CAD integration domain, covering file management, connection handling, execution, knowledge retrieval, and user feedback. Each tool earns its place, and the count sits at the upper bound of the ideal range without feeling bloated.

    Completeness5/5

    The tool surface covers the full lifecycle: file bootstrap (create, open, wait), generic execution via execute_cadwork_command, connection status, session storage, user notes/messages, and knowledge support. The generic executor handles any missing specific operation, and no obvious gaps cause dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources