SolidWorks MCP connects Claude Desktop or Claude Code to SolidWorks through a local Python server and the Windows COM API. The alisamsam/Solidworks-MCP repository presents it as an MCP server for automating SolidWorks with natural language, covering connection, document, sketch, feature, and utility tools. At the GitHub check on August 26, 2026, the repository was MIT licensed, had 100 stars and 20 forks, and its README stated compatibility with SolidWorks 2023 through 2025.
For Educasium, this connector is less central than Revit MCP or Archicad MCP, because SolidWorks is mainly used for mechanical design, product design, furniture, assemblies, and fabrication. It is still useful for explaining how an AI assistant can turn a text instruction into controlled parametric geometry, provided the work stays on test files and under the supervision of a responsible CAD operator.
Table of Contents
- What SolidWorks MCP does
- Installation and architecture
- Useful design capabilities
- Comparison with CAD and BIM MCPs
- Security, governance, and limits
- Educasium position
- Sources and next reading
What SolidWorks MCP does
Key point: SolidWorks MCP gives Claude a local action interface for SolidWorks, but it is not a Dassault Systèmes certified copilot. The README documents 22 tools, while the verified server file also exposes a few additional helpers such as document information, face-based sketch creation, and sketch diagnostics.
Documented tool surface
The README groups the tools into four families. Connection covers connect_solidworks and get_solidworks_info. Documents cover create_new_part, create_new_assembly, open_document, close_document, save_document, and list_open_documents. Sketches cover create_sketch, close_sketch, draw_circle, draw_rectangle, draw_line, draw_arc, and draw_polygon. Features cover extrude_sketch, cut_extrude, fillet_edges, chamfer_edges, and list_features. Utilities cover set_units and execute_python.
This list already enables a full workflow for a simple part: open SolidWorks, create a document, draw a sketch, extrude it, add fillets or chamfers, list the features, and save. The promise is not only conversational. It concerns real CAD operations in an active SolidWorks session.
What the code adds beyond the README
The verified solidworks_mcp/server.py file identifies version 4.0.0 with fixes for SolidWorks 2025. It adds get_document_info, create_sketch_on_face, and get_sketch_status to the observed surface. That difference is not necessarily a problem, but it shows why an MCP should be evaluated from the code as well as the README.
The server also exposes execute_python, which runs Python with access to the SolidWorks application, the active document, the automation object, the win32com and pythoncom COM libraries, and math, os, and json. It is the repository's most powerful capability. It is also the capability that changes the risk level: an assistant can leave the predefined tool perimeter and act through arbitrary code.
Installation and architecture
Key point: SolidWorks MCP is a local Windows connector based on Python, pywin32, and SolidWorks COM automation. It requires an installed SolidWorks license and does not work as an independent cloud service.
Verified requirements
The README requires Windows 10 or Windows 11, SolidWorks 2023, 2024, or 2025 installed and licensed, Python 3.10 or higher, and Claude Desktop or Claude Code. The verified requirements.txt lists mcp version 1.0.0 or higher, asyncio-compat, python-dotenv, and pywin32 version 306 or higher. It also notes that pythoncom is included with pywin32.
Those requirements naturally narrow the audience. A firm or school working on macOS, Rhino, Revit, or Archicad cannot reuse this MCP unchanged for its main environment. It is primarily for a Windows workstation where SolidWorks is already present, activated, and available for COM automation.
Detection and configuration
The README says the server can auto-detect SolidWorks through the Windows registry. The verified config.json keeps exe_path on auto, sets the startup timeout to 120 seconds, max retries to 3, default unit to mm, and defaults such as 10 mm extrusion, 2 mm fillet, and 2 mm chamfer. These settings make the server more predictable for a demonstration.
The typical launch path is to clone the repository, install Python dependencies, configure Claude Desktop with the Python entry pointing to solidworks_mcp_server.py, open SolidWorks, and ask Claude to connect. The chain is easy to explain, but it is not frictionless. Between Python, the MCP client, SolidWorks state, document templates, and Windows permissions, a serious test should use a dedicated workstation.
Useful design capabilities
Key point: the connector is relevant for simple parts, repetitive operations, and demonstrations of AI-driven parametric design. It becomes more sensitive when it touches real assemblies, client files, or production details.
Parts, sketches, and features
Sketch tools cover standard primitives: circle, rectangle, line, arc, and polygon. Feature tools can extrude, cut extrude, apply a fillet or chamfer, and read model features. For a course or workshop, this progression is readable: the learner sees how an intention becomes a sketch, then a volume, then a detail.
In a product design team, this type of interface can help produce quick variants of a simple geometry. For example, an operator can ask for a test part, compare multiple extrusion depths, generate repetitive forms, or verify the feature list before saving. This should not be turned into an automatic industrialization claim: edge selection, sketch quality, and functional logic still need to be checked in SolidWorks.
SolidWorks 2025 compatibility
The README highlights API fallbacks for SolidWorks 2025, especially a FeatureExtrusion3 to FeatureExtrusion2 to FeatureBossSimple chain. The verified server also mentions fixes for closing sketches before extrusion, cut extrudes, feature property access, and stdout or stderr capture in execute_python. These are technical details, but they matter in an evaluation.
They show that the repository has encountered behavioral differences between SolidWorks versions and tries to absorb them in code. For a decision-maker, the conclusion is not that everything is guaranteed. The conclusion is that a pilot must test the company's exact SolidWorks version, templates, macros, network paths, and saving rules.
Comparison with CAD and BIM MCPs
Key point: SolidWorks MCP is a mechanical CAD connector, not a building BIM connector. It compares better with FreeCAD MCP or AutoCAD MCP than with a production Revit workflow.
| Option | Natural use | Main strength | Limit to watch |
|---|---|---|---|
| SolidWorks MCP | Parts, sketches, features, and simple assemblies | Local COM API, concrete CAD operations, stated 2023-2025 compatibility | Windows, SolidWorks license, execute_python, human validation |
| FreeCAD MCP | Open-source prototyping and CAD training | Open Python, parametric objects, possible FEM | Less standard in firms, variable workflow maturity |
| AutoCAD MCP | 2D drawing, DXF, and AutoCAD LT automation | AutoCAD LT backend and headless DXF backend | Less focused on product parametric design |
| Revit MCP | Building BIM model | Walls, floors, doors, rooms, levels, and data extraction | Strict BIM governance and Revit dependency |
Difference from FreeCAD MCP
FreeCAD MCP is more open and experimental, because FreeCAD and Python allow users to understand or modify many things without a proprietary license. SolidWorks MCP is closer to an existing industrial workstation, with a commercial application already adopted by mechanical offices. The choice therefore depends less on AI and more on the CAD environment already in place.
For training, FreeCAD can be more accessible if the goal is to demonstrate principles. SolidWorks becomes more relevant when the learner or company already works on parts, assemblies, sheet metal, tooling, or components in that ecosystem. In both cases, the assistant does not replace CAD literacy: it accelerates some actions and makes the workflow more conversational.
Difference from Revit MCP
Revit MCP handles building objects: walls, floors, doors, rooms, grids, levels, and schedules. SolidWorks MCP primarily handles shapes and features for mechanical design. For an architecture firm, SolidWorks may appear in furniture details, prototypes, custom parts, objects, or manufacturer coordination, but it is not the core BIM platform.
This difference should shape the content strategy. A SolidWorks MCP page attracts readers interested in AI applied to technical CAD, not only architecture. It broadens the Educasium library, but it must not imply that Educasium has integrated SolidWorks MCP in a real client project.
Security, governance, and limits
Key point: the main risk is running real actions in an open design application, especially with execute_python. A pilot should start on disposable files, never on a client production model.
Destructive actions and open files
The server can open, close, and save documents. It can also modify part geometry through extrusion, cuts, fillets, or chamfers. A poorly framed instruction, wrong edge selection, or misunderstood unit can produce an incorrect file without making the error obvious at first glance.
Minimum governance means using a test folder, copying source files, disabling uncontrolled automatic saves, keeping a prompt log, and having a CAD lead validate results. In a professional environment, open and save tools must be treated as sensitive permissions, not simple conveniences.
execute_python should be reserved
execute_python gives access to os and to SolidWorks COM objects. It is not just a drawing tool. It is a path to arbitrary Python code in the context of the local machine and CAD session.
For education, it can demonstrate advanced automation under supervision. For firm use, it should be reserved for a technical profile, enabled only on a pilot workstation, and excluded from scenarios where a non-specialist assistant works on client data. If the goal is to train architects or designers who are not developers, the predefined tools are easier to govern.
Educasium position
Key point: Educasium can present SolidWorks MCP as a credible example of AI-driven CAD automation, but without claiming internal or client deployment. At this stage, the analysis is based on the GitHub repository, not an Educasium field report.
What we can say
We can say that the repository exists, is MIT licensed, targets SolidWorks 2023 through 2025, uses Python and pywin32, has a README documenting 22 tools, and has verified source code exposing a few additional helpers. We can also say it automates concrete CAD operations such as creating a part, drawing a sketch, extruding, cutting, applying fillets or chamfers, listing features, and saving.
We should not say that Educasium has deployed it for a client, that it reduces design time by a given percentage, or that it is safe by default. Those claims would require a test protocol, files, measurements, and domain validation. Without that evidence, they would be marketing rather than verifiable information.
Hypothetical implementation
A hypothetical implementation would start on an isolated Windows workstation with SolidWorks 2025 or the company's exact version. The CAD lead creates a blank part and tests connect_solidworks, get_solidworks_info, create_new_part, create_sketch, draw_rectangle, extrude_sketch, list_features, and save_document in a test folder. execute_python, open_document, and close_document stay disabled or reserved until the basic flow is understood.
The second step would be to document successful prompts, unit errors, selection behavior, and generated files. The third would be to decide whether the use remains educational, exploratory, or genuinely productive. Without that separation, a powerful connector quickly becomes difficult to govern.
Sources and next reading
Key point: this page was written from GitHub sources checked on August 26, 2026. Star and fork counts can change, but the technical requirements and execute_python risk should be rechecked before any client recommendation.
To continue the comparison, read AutoCAD MCP, FreeCAD MCP, and Revit MCP. SolidWorks MCP is interesting because it shows an assistant acting inside a very concrete technical design application. Its value will depend less on an AI slogan than on the quality of the frame: pilot workstation, test files, limited permissions, CAD validation, and operation logging.