Skip to main content
Glama
andrewbartels1

SolidworksMCP-python

Related Servers

Alternatives to SolidworksMCP-python

No user-submitted related servers found.

    Related Servers

    • 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
    • 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.
      -
    • 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
    • A
      license
      Not graded
      quality
      C
      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.
      1
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients like Claude to automate SOLIDWORKS 2025 and SOLIDWORKS CAM via COM, covering parts, assemblies, drawings, and CAM toolpaths. It generates real geometry, mass properties, and posted G-code files directly on disk.
      40
      MIT

    TDQS

    C2.3/5.0

    Scored across 112 tools

    Disambiguation1/5

    Many tools are near-duplicates or aliases: get_mass_properties/calculate_mass_properties, start/stop_macro_recording vs automation_start/stop_macro_recording, generate_vba_code vs specific generate_vba_* tools, and create_drawing_view vs add_drawing_view vs create_technical_drawing. The drawing analysis/check/validation cluster also has heavily overlapping boundaries (check_drawing_standards, check_drawing_compliance, validate_drawing_completeness, analyze_drawing_complehensive). An agent cannot reliably pick the intended tool.

    Naming Consistency2/5

    Most names follow a rough verb_noun shape, but the verb vocabulary is inconsistent: create_* vs add_* for similar drawing/view operations, get_* vs calculate_* for identical mass properties, and start_macro_recording vs automation_start_macro_recording are divergent aliases. Some names are verb noun_verb_gerund, like automation_start_macro_recording, which breaks the pattern.

    Tool Count1/5

    112 tools is far beyond what the server's purpose warrants. Many are duplicate, alias, or near-duplicate operations, plus entire hobby-horse families for VBA code generation, template management, macro management, and drawing auditing. The surface is bloated rather than scoped.

    Completeness2/5

    Despite the huge tool count, core SolidWorks assembly workflows are missing: there is no direct tool for inserting components or applying assembly mates (only VBA code generation helpers). Feature editing/deletion is also absent. The surface is broad on drawing analysis, teplates, and macros but has significant dead ends in the primary modeling/assembly domain.

    Maintenance

    ActivityActive
    ResponsivenessSlow