Skip to main content
Glama
danielproxd2

MCP_CAD

by danielproxd2

Related Servers

Alternatives to MCP_CAD

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for controlling a live SOLIDWORKS session through the Windows COM API, enabling native CAD operations like sketches, features, bodies, views, and exports, plus transactional plans and vectorization.
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that controls SolidWorks via COM, enabling CAD automation with 138 tools for sketching, 3D features, assemblies, drawings, and more.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP bridge server for SolidWorks that enables AI assistants to control SolidWorks programmatically via COM automation.
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Python MCP server for SolidWorks automation with 109 tools covering the full CAD lifecycle. Enables AI-assisted design workflows through COM automation on Windows.
      100
      79
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that drives SolidWorks 2023+ on Windows, exposing CAD operations like sketching, extrusions, assemblies, and exports through tools for AI assistants like Kimi and Claude.
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that integrates local LLMs (via Ollama) with SolidWorks through its COM API, enabling read-only inspection of features, dimensions, equations, mass properties, and file exports. It supports models like Qwen3 and plans future expansion to editing and generation.
      -

    TDQS

    A3.6/5.0

    Scored across 100 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes with detailed descriptions. There are a few overlapping pairs (e.g., verify_against_spec and verify_build_report, break_all_edges and fillet_all_edges), but the descriptions help differentiate them. Overall, an agent can distinguish tools with reasonable accuracy.

    Naming Consistency3/5

    Many tools follow a consistent verb_noun pattern (create_, add_, build_, list_, get_, set_, run_, record_, verify_), but there are deviations like 'break_all_edges', 'hole_wizard', 'place_and_mate', and 'stack_components'. The mix of underscores and no underscores creates some inconsistency, but the patterns are still readable.

    Tool Count2/5

    With 100 tools, the server is extremely large. While each tool serves a specific purpose, the sheer number is excessive for most workflows and may overwhelm users. Many tools are composites or niche functions that could be combined. The count far exceeds the typical well-scoped range of 3-15 tools.

    Completeness4/5

    The tool set covers a wide range of CAD operations including part creation, assembly, modification, measurement, verification, batch processing, macros, and catalog search. There are minor gaps (e.g., no direct tool for editing sketch geometry post-creation beyond dimensions), but overall the surface is comprehensive for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues