Skip to main content
Glama
rdolan5

solidworks-mcp

by rdolan5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to solidworks-mcp

No user-submitted related servers found.

    Related Servers

    • solidworks-mcp

      yimu0824
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP bridge server for SolidWorks that enables AI assistants to control SolidWorks programmatically via COM automation.
      MIT

    • SolidworksMCP

      czuryk
      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.
      3
      MIT

    • solidworks-mcp

      keecherr
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI (e.g., Claude) to control SolidWorks via natural language, automating part creation, sketching, and feature operations through the Model Context Protocol.
      1
      MIT

    • mcp-solidworks

      h4child
      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

    • solidworks-mcp

      yezg9920-kely
      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.
      -

    • SolidWorks MCP Bridge

      Said-AER
      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.
      -
    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.4/5.0

    Scored across 40 tools

    Disambiguation4/5

    Most tools are clearly distinct by domain (sketch, feature, pattern, assembly, etc.), and the dispatcher design groups related operations under a single tool. However, generic tools like solidworks_api and solidworks_script overlap with all other tools, and legacy tools (solidworks_sketch_begin, solidworks_cam_workflow) partially duplicate functionality, creating minor selection ambiguity.

    Naming Consistency4/5

    All tools share the 'solidworks_' prefix and use snake_case, with names clearly indicating their purpose. The pattern is consistent, though there is a mix of verb-led (connect, open, save) and noun-led (active_document, assembly_tree) names, and legacy tools like sketch_begin vs sketch and cam_workflow vs cam introduce slight inconsistency.

    Tool Count3/5

    With 40 tools, the count is above the typical 3–15 range and exceeds the 25+ heavy threshold. However, the domain (full CAD/CAM automation) is extensive, and many tools are dispatchers covering multiple operations, so the number is justifiable, though it feels heavy for an agent to navigate.

    Completeness5/5

    The tool set covers document lifecycle, sketching, features, patterns, assemblies, parametric equations, materials, configurations, analysis, drawings, CAM, and persistent references. The inclusion of generic API and script tools ensures no capability gap, making the surface effectively complete for the stated SOLIDWORKS automation purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources