Skip to main content
Glama
Sign In
SolidworksMCP-python

SolidworksMCP-python

by andrewbartels1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to SolidworksMCP-python

No user-submitted related servers found.

    Related Servers

    • 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

      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

    • solidworks-mcp

      yezg9920-kely
      F
      license
      Not graded
      quality
      D
      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.
      1
      -

    • swagent

      lius-101504
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that lets an AI agent drive a local SOLIDWORKS installation over COM, covering sketching, extrude/revolve, holes and counterbores, patterns, mirror, shell, fillet/chamfer, assemblies, drawings and configurations, plus save, export and screenshot. Every modelling call returns a measured volume and fails loudly if the geometry did not actually change, so silent no-ops are caught.
      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

    • SolidworksMCP

      czuryk
      A
      license
      Not graded
      quality
      B
      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.
      10
      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

    C2.7/5.0

    Scored across 154 tools

    Disambiguation2/5

    Many tools are functionally indistinguishable or duplicate aliases: get_mass_properties is literally a 'backward-compatible alias' for calculate_mass_properties, start_macro_recording/stop_macro_recording duplicate automation_start_macro_recording/automation_stop_macro_recording, batch_process_files vs batch_file_operations vs batch_export vs convert_file_format heavily overlap, and create_drawing / create_technical_drawing / generate_drawing_package all claim to produce drawings. add_dimension vs add_sketch_dimension vs insert_model_dimensions vs auto_dimension_view and the seven analyze_drawing_* / check_drawing_* tools are also hard to separate. Only the core sketching and modeling primitives (add_line, add_circle, exit_sketch, create_sketch) have clearly distinct purposes.

    Naming Consistency3/5

    The dominant pattern is snake_case verb_noun (create_part, export_step, add_fillet), which is good, but there are notable deviations: adjective-suffixed names like analyze_drawing_comprehensive and analyze_geometry ('Handle analyze geometry'), prefix variants automation_start_macro_recording vs start_macro_recording, noun-first tutorial names (sketch_tutorial_simple_hole vs tutorial_simple_hole), and several bare/ambiguous verbs (undo, save_as). The parallel generate_vba_* family is consistent, but the duplication of naming across prefixes suggests two conventions merged.

    Tool Count1/5

    154 tools is an extreme mismatch for a single MCP server — roughly ten times a well-scoped surface. Whole clusters (11 generate_vba_* tools, 9 analyze_drawing_* tools, a macro recording API duplicated twice, a template library suite, and an API-doc lookup suite) could be collapsed or moved out. Many of these tools clearly do not earn their individual place.

    Completeness4/5

    Coverage of the CAD lifecycle is genuinely broad: document creation/open/save, sketching primitives, boss and cut features, fillets/chamfers/patterns/mirror, assemblies with mates and interference checks, drawings with views, dimensions, GD&T and BOM, mass properties, and many export formats. Minor gaps exist — mating is limited to reference planes/axes, angled reference planes are unsupported, and no couple-level assembly mirror, but no major workflow dead end.

    Maintenance

    ActivityActive
    ResponsivenessLimited data

    Resources