Skip to main content
Glama
Psalmustrack

lambdacad-mcp

by Psalmustrack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to lambdacad-mcp

No user-submitted related servers found.

    Related Servers

    • AutoCAD MCP Server

      gpt2nndk
      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

    • AutoCAD MCP Server

      gpt2nndk
      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

    • Q3DS SolidWorks MCP

      zarcherlot
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server enabling AI-driven CAD automation for SolidWorks at the feature level, converting intent into CAD-neutral IR and compiling it into concrete operations. It provides engineering-semantic tools and a deterministic compiler, bridging any MCP-capable AI client to SolidWorks via COM.
      AGPL 3.0

    • multiCAD-mcp

      sophiei7183
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables controlling CAD applications such as AutoCAD, ZWCAD, GstarCAD, and BricsCAD through AI assistants, providing drawing, layer, entity, block, data export, file, and session operations via unified MCP tools.
      -

    • AutoCAD MCP Server

      cristoferlabs
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that bridges Claude with AutoCAD, enabling to generate architectural floor plans, draw geometry, and export DXF files just by describing what you need in natural language.
      -
    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.3/5.0

    Scored across 128 tools

    Disambiguation4/5

    Almost every tool has a clearly distinct purpose, and descriptions often explicitly contrast related tools (e.g., rotate_3d vs rotate_entity, hatch_circle vs hatch_islands). With 128 tools there are some potentially confusable pairs like get_entity_counts vs drawing_info, but the detailed explanations resolve most ambiguity.

    Naming Consistency4/5

    The naming is largely consistent, with clear families such as draw_*, solid_*, bool_*, list_*, get_*, set_*, and assembly_*. Minor deviations like 'regen', 'leader', 'polygon', and the mixed bool/boolean (bool_union vs boolean_verified) prevent a perfect score.

    Tool Count1/5

    With 128 tools, this is an extreme outlier for an MCP server. Even for a broad CAD domain, the surface is overwhelming and far exceeds the 3-15 tool guideline, making tool selection costly and impractical for agents.

    Completeness5/5

    The toolset covers virtually every CAD operation: 2D drafting, 3D solids, editing, dimensions, layers, blocks, viewports, sheets, exports, rendering, analysis (interference, holes, overhang), assembly management, graph analysis, and a memory system. There are no obvious dead ends, and run_command/run_lisp fill any hypothetical gaps.

    Maintenance

    ActivityNo data
    ResponsivenessUnresponsive

    Resources