SolidWorks MCP Python
Related Servers
Alternatives to SolidWorks MCP Python
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI models to automate SolidWorks CAD at the feature level through MCP, including building parts from DXF/DWG drawings and reproducing existing parts via a deterministic compiler.1AGPL 3.0
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to control supported CAD applications through natural-language instructions and unified MCP tools for drawing, layers, blocks, entities, files, and data export.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to build and edit native CAD parts and assemblies, inspect saved geometry and measurements, retain revisions, run mechanism and interference checks, and export STEP/STL/GLB artifacts through MCP tools.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible agents to drive SolidWorks for validated modeling, GB material assignment, assembly mates, exact interference checks, and GB-standard drawing production with read-back verification.248 PyPI29MIT
- AlicenseBqualityDmaintenanceEnables connecting MCP clients to local SolidWorks for automated 3D part creation, template generation, file export, and basic review via natural language.104MIT
- AlicenseBqualityCmaintenanceEnables Claude or any MCP client to drive a live SOLIDWORKS session through its COM API, modeling parts, building assemblies with mates, checking interferences and machining feasibility, and exporting STEP or DXF files. It also exposes a local semantic index of the SOLIDWORKS API so the model can look up signatures, enums, and official examples before running arbitrary Python against the session.222MIT
TDQS
Scored across 157 tools
Each tool's description explicitly states its purpose and cross-references alternatives, which keeps most selections clear, but the surface carries several genuine near-duplicates: load_part/load_assembly vs open_model, save_part/save_assembly vs save_file, get_file_properties vs get_model_info, calculate_mass_properties vs get_mass_properties, and add_drawing_view vs create_drawing_view. Deprecated aliases mitigate the risk by naming their replacement, but an agent can still land on the superseded tool. The nine generate_vba_* tools plus create_* equivalents form another cluster that only the prose keeps apart.
Names are uniformly snake_case with a verb-led convention across most of the surface (create_, add_, list_, get_, set_, export_, generate_, check_, verify_). A minority are noun-led or bare-noun patterns (sketch_mirror, sketch_trim, pattern_linear, mirror_feature, measure_entities), and add_fillet/add_chamfer vs add_sketch_fillet/add_sketch_chamfer show the sketch/solid split is expressed inconsistently. Still highly readable with only minor deviations.
157 tools is far beyond a manageable surface; even for a full CAD application this is a large, layered API exposed at once. Deprecated aliases (load_part, save_part, calculate_mass_properties, get_file_properties, add_drawing_view, sketch_tutorial_simple_hole) and the redundant generate_vba_* family inflate the count without adding capability. The breadth of sub-domains justifies many tools, but not this many, and grouping/packs would help.
Coverage is unusually deep: sketching primitives and constraints, boss/cut extrude, revolve, sweep, loft, fillet/chamfer/draft/rib/shell, hole wizard, sheet metal with flat pattern and DXF export, assembly mates/components/patterns/interference, drawings with views, dimensions, GD&T, BOM, and a wide export set. Remaining gaps are modest (no cut-sweep/cut-loft, no body delete or combine/split beyond save_body_as_part, no delete_custom_property, no component delete), which agents can route around or handle via macros.