solidworks-mcp-python
Related Servers
Alternatives to solidworks-mcp-python
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables Claude to create and manipulate SolidWorks CAD models through natural language commands, automating part creation, sketching, and extrusion.10-
- AlicenseBqualityBmaintenanceEnables 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.40MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI (e.g., Claude) to control SolidWorks via natural language, automating part creation, sketching, and feature operations through the Model Context Protocol.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to build, measure, verify, and correct parametric SolidWorks parts and assemblies locally via the COM API, supporting operations like sketching, extruding, modeling, dimensioning, material assignment, export, and assembly mating.MIT
- AlicenseBqualityDmaintenanceEnables connecting MCP clients to local SolidWorks for automated 3D part creation, template generation, file export, and basic review via natural language.103MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to automate SolidWorks (open/save parts, modify dimensions, export STEP) via COM, and optionally generate geometry using build123d code-CAD with PNG previews.MIT
TDQS
Scored across 22 tools
Each tool targets a distinct operation or resource, with the five sw_api_* tools clearly differentiated by purpose (search, doc, enum, members, example). Minor overlap exists between sw_bbox and sw_list_bodies (both report bounding boxes) and between sw_save_as (which can optionally export STEP) and sw_export_step, but descriptions disambiguate well.
All tools use a consistent sw_ snake_case prefix, making them easy to recognize as part of the same server. However, the verb style varies: some are verb-first (sw_list_features, sw_open) while others are noun-first (sw_bbox, sw_mass_properties), a minor deviation from a pure verb_noun pattern.
With 22 tools, the set is on the heavier side for a typical MCP server, but the breadth of SolidWorks automation (modeling, assembly, machining check, and API introspection) justifies most tools. No tool feels redundant enough to warrant removal, though some merging (e.g., bbox into list_bodies) could reduce count.
The server covers document lifecycle (new, open, save, close, export), inspection (bbox, mass, features, bodies), assembly interferences, and machining checks. Direct modeling tools are sparse (only extrude), but sw_execute_script plus extensive API documentation provides a complete escape hatch for any missing operation, leaving no dead ends.