SolidWorks and AI for 3D CAD: Software, Hardware, and Setup
Share
Updated 12 November 2026. SOLIDWORKS does not ship a single “AI button” that replaces a designer. You pick one of three setups: Dassault’s companions inside the session, a community MCP server that drives the open SOLIDWORKS window, or a file review where the model only sees STEP and PDF exports. Each setup has its own PC, license, and safety rule.
In short
- Native path: AURA and LEO in SOLIDWORKS Design 2026 SP3.2 or later, signed in to the 3DEXPERIENCE platform, with the Collaborative Designer for SOLIDWORKS role. LEO works on the open model. AURA answers from knowledge and documents.
- Agent path: A Windows PC with a licensed SOLIDWORKS session already open, Python 3.10 or newer on that same Windows install, and an MCP client such as Claude Desktop or Claude Code. There is no official Claude connector. Community servers are not Dassault products.
- PC: x86_64 Intel or AMD, Windows 11 64-bit, 32 GB RAM as the practical minimum, 64 GB when a local model shares the box, an SSD, and a SOLIDWORKS-certified GPU. Cloud models do not need a second GPU. A local model does.
- First week: one copied part, read-only tools, then a short feature list. Check mass, mates, and the drawing before anyone treats the file as design output.
Three ways AI touches a SOLIDWORKS file
| Setup | What the model can do | What you must already have | Best first use |
|---|---|---|---|
| AURA and LEO | AURA: questions, documents, SOLIDWORKS know-how. LEO: assembly structure, image-to-mesh, features on a STEP file, assembly checks, error cleanup, inside the session. | SOLIDWORKS Design 2026 SP3.2 or later, 3DEXPERIENCE login, Collaborative Designer role. Named-user Design, or Design with Cloud Services on a device-locked license. | Daily modeling help without installing a second server. |
| MCP on the workstation | Tools over stdio or localhost that call the SOLIDWORKS COM API: read the open part, add features, export. | Windows, SOLIDWORKS running, Python 3.10+ with pywin32, an MCP client. Match the server to the SOLIDWORKS year it was tested on. | Repeatable edits on a sandbox part, with a human watching the feature tree. |
| Export review | The model reads STEP, Parasolid, or a drawing PDF. It does not click SOLIDWORKS. | Any PC that can open the chat client. A Mac can do this job. It cannot run SOLIDWORKS. | Design review notes, BOM questions, drawing checks. |
Board layout is a different stack. If the product also has a PCB, use the KiCad and Altium MCP guide beside this one. Mechanical CAD and PCB CAD should not share one unattended agent.
Hardware requirements
Dassault’s client matrix for SOLIDWORKS 2025 through 2027 asks for an x86_64 processor (Intel 64 or AMD64), 16 GB of RAM with 32 GB recommended, a certified graphics card and driver, and an SSD. PDM Contributor, PDM Viewer, and Electrical Schematic are listed lower, at 8 GB with 16 GB recommended. Virtual machines are listed separately. SOLIDWORKS and eDrawings want a GPU in a virtual machine. Composer is not supported there.
Those numbers are the CAD floor. An AI session adds the chat client, often a browser, and sometimes a local model. Size the workstation for the heaviest pair you will run at once.
| Job | RAM | GPU | Disk | Notes |
|---|---|---|---|---|
| SOLIDWORKS only, small parts | 32 GB | Certified workstation card | 1 TB NVMe SSD | Meets the published recommendation with headroom for Chrome and Office. |
| SOLIDWORKS plus a cloud model (Claude, GPT, Gemini) | 32 GB, 64 GB if assemblies are large | Same certified card. No CUDA card required for the model. | 1 TB NVMe, models on a local folder, not the vault | The model runs in the vendor cloud. Your PC only hosts SOLIDWORKS and the MCP process. |
| SOLIDWORKS plus a local model | 64 GB | Certified CAD card, plus an NVIDIA card with 16 GB VRAM or more if the model is local | 2 TB NVMe | Keep the CAD driver certified. Do not replace it with a gaming driver to chase model speed. |
| Image or sketch vectorization inside a community server | 64 GB | NVIDIA CUDA when the server says so | 2 TB NVMe | SolidworksMCP documents CUDA for deep vectorization. Basic COM tools do not need it. |
Buy the GPU from the certified list for your exact SOLIDWORKS year and service pack. A fast game card can be slower, or unsupported, in RealView and drawings. Put Windows, SOLIDWORKS, and the working folder on the SSD. Leave PDM archive disks to the PDM admin.
New seats should use Windows 11 64-bit. Dassault’s matrix still documents Windows 10 support windows by product year. Confirm your service pack on the system requirements page before you image a lab. Office 2021 or 2024 covers the Excel and Word links many design tables use. 64-bit Office is the recommended side.
A Mac is not a SOLIDWORKS workstation. eDrawings has a Mac build. Parallels appears on the hypervisor list for some years. For AI plus live modeling, use a Windows PC. Use the Mac only for the export-review path.
Software requirements
1. SOLIDWORKS and the platform
- Install SOLIDWORKS Design and update to 2026 SP3.2 or later if you want AURA and LEO. Hawk Ridge’s setup note uses that service-pack floor.
- Connect the seat to your company 3DEXPERIENCE platform. Named-user licenses launch from the platform or a desktop shortcut. Device-locked Cloud Services seats sign in from the 3DEXPERIENCE task pane.
- Ask the platform admin for the Collaborative Designer for SOLIDWORKS role.
- Open a part. Open the Virtual Companions tab. AURA can also be opened from the platform without SOLIDWORKS. LEO only runs inside SOLIDWORKS, because its skills use the loaded model.
- Budget Blue tokens. Hawk Ridge states that tokens are consumed when a companion runs a skill and returns a result. Typing in the panel does not, by itself, consume tokens.
2. MCP client and Python
Use this path when you want Claude, or another MCP client, to call SOLIDWORKS tools. Install Python on Windows, not in WSL. WSL cannot see the SOLIDWORKS COM server.
- Python 3.10 or newer. One public server, SolidworksMCP, acceptance-tests 3.11.
- Git, and Git LFS if the server ships model weights.
- .NET Framework 4.8 and Visual Studio 2022 Build Tools if you choose SolidPilot (eyfel/mcp-server-solidworks), which targets SOLIDWORKS 2026 and a C# execution layer.
-
uvif you choose MCP_CAD (danielproxd2/solidworks-mcp). That project talks to COM through pywin32 and can fall back to a mock mode for tests. - Claude Desktop config at
%APPDATA%\Claude\claude_desktop_config.json, or Claude Code’s MCP settings. The browser chat at claude.ai cannot start a process on your PC.
Point the client at the virtual environment’s python.exe with a full path. Restart the client after every config edit. Start SOLIDWORKS first, open a part, then start the client.
3. What not to install on the CAD PC
- Do not point an MCP server at a PDM vault root or a shared drive of released parts.
- Do not enable a tool that runs arbitrary Python, or that listens on
0.0.0.0, until you have read the server code. Bind local servers to127.0.0.1. - Do not mix a gaming GPU driver over the top of a certified SOLIDWORKS driver.
Setup guide: cloud model, live SOLIDWORKS
This is the setup most hardware teams should try first. The model is Fable, Opus, or another hosted model. The PC does not load model weights.
- Confirm the license and SP level. Help, About. You want 2026 SP3.2 or later for companions. For MCP, note the year and match it to the server’s README.
- Create a sandbox folder outside PDM, for example
D:\ai-sandbox\bracket-001\. Copy one part into it. Do not check that copy out from a released revision. - Open the copy in SOLIDWORKS. Leave the default template units visible. Write them in the chat: millimeters, and the material.
- If you use companions: sign in to 3DEXPERIENCE, open Virtual Companions, and ask LEO for a read-only description of the open part before you ask it to add a feature.
- If you use MCP: clone the server, create a venv, install requirements, and add the stdio entry. Example shape, with your own paths:
{
"mcpServers": {
"solidworks": {
"command": "C:\\cad-ai\\solidworks-mcp\\.venv\\Scripts\\python.exe",
"args": ["C:\\cad-ai\\solidworks-mcp\\server.py"]
}
}
}
- Restart the MCP client. Ask it to list tools and to report the active document name. Stop if the name is not the sandbox file.
- Give one constrained task: “Add a 3 mm through hole, 10 mm from the left edge and 8 mm from the bottom edge, on the front face. Do not change other features.”
- Rebuild. Read the feature tree. Measure the hole. Check mass properties against the number you expect.
- Save a Pack and Go of the sandbox. If the result is wrong, close without saving, or roll the feature back. The chat log is not a revision.
- Only after three clean edits, decide whether that server is allowed to create new files. Keep exports (STEP, drawing PDF) in the same sandbox so a second reviewer can open them without SOLIDWORKS.
Setup guide: file review, no live CAD control
Use this when the designer is on a locked-down PC, or when you only want notes.
- Save STEP AP214 and a PDF of the drawing from the sandbox part.
- Upload those files to the model chat. State units, material, and the load case in one paragraph.
- Ask for a list of risks: thin walls, missing draft, undercuts, fastener stack, and drawing dimensions that do not match the model.
- The designer applies any accepted change in SOLIDWORKS. The model does not get a license or a COM handle.
This path is also how a Mac user participates. Review files. Do not expect the model to open .sldprt by itself unless a Windows agent with a shell is in the loop, and even then treat native-file parsing as a leak risk. STEP and PDF are the files you meant to share.
How to prompt a CAD model
Write prompts like a junior engineer’s task ticket.
- Name the document, the configuration, and the units.
- Name the face or plane in words the feature tree already uses.
- Give numbers and datums. “Make it stronger” is not a task. “Add a 2 mm rib on Plane3, from the boss to the outer wall” is a task.
- Ask for a rebuild and a mass delta after each edit.
- Forbid silent template changes, unit changes, and deletes of absorbed sketches unless you asked for that delete.
Long, open-ended modeling sessions are where a frontier model earns its cost. Day-to-day questions can stay on a smaller model. Our Fable 5.2 and Mythos 5.2 note separates those roles. BenchCAD scores there are about reconstruction from drawings, not a SOLIDWORKS leaderboard. Do not treat them as a mate-success rate inside your assembly.
What to check before the file leaves the sandbox
- Units and material. A hole that is 3 inches in a millimeter part is a scrap part.
- Feature tree. No suppressed surprises, no duplicate bodies, no external references into someone else’s folder.
- Mates. Fully defined, or the remaining degrees of freedom are the ones you wanted.
- Mass and center of gravity. Compare to the previous revision.
- Drawing. Views, dims, and the title block still match the model.
- DFM. Draft, wall thickness, and fastener access against your contract manufacturer’s process, not against the default template.
If the product is a mechanism, the model is still not the actuator, the driver, or the fixture. Those sit in the actuator guide and in Physical AI engineering when the CAD, the board, and the robot have to ship together. Firmware that reads sensors on that mechanism belongs with embedded systems and firmware.
A practical bill of software
| Piece | Required for companions | Required for MCP | Required for file review |
|---|---|---|---|
| Windows 11 64-bit | Yes | Yes | No |
| SOLIDWORKS Design 2026 SP3.2+ | Yes | A year the server documents | Only on the designer’s PC, to export |
| 3DEXPERIENCE login and Collaborative Designer | Yes | No | No |
| Python 3.10+ on Windows, venv | No | Yes | No |
| MCP client | No | Yes | No |
| .NET Framework 4.8 and MSBuild | No | Only for C# servers such as SolidPilot | No |
| Certified GPU driver | Yes | Yes | No |
FAQ
Can I run SOLIDWORKS AI on a Mac?
Not as a live modeling session. SOLIDWORKS is a Windows application. Use a Windows workstation for AURA, LEO, and MCP. A Mac can review STEP and PDF exports in a chat client.
Do I need a high-end NVIDIA card for Claude or GPT?
No. Hosted models run in the vendor cloud. You still need a SOLIDWORKS-certified GPU for the CAD view. Add a CUDA card only if you run a local model or a server feature that states it uses CUDA.
Which SOLIDWORKS version do AURA and LEO require?
SOLIDWORKS Design 2026 SP3.2 or later, connected to 3DEXPERIENCE, with the Collaborative Designer for SOLIDWORKS role. LEO is only inside the SOLIDWORKS session. AURA can also open from the platform.
Is there an official Claude or ChatGPT plug-in from Dassault?
No. Companions are Dassault’s own UI. MCP servers on GitHub are community projects. They are not endorsed by Dassault. Read the tool list, run them on copies, and keep them off the vault.
How much RAM should we buy in 2026?
32 GB is the right minimum for SOLIDWORKS plus a cloud assistant. Buy 64 GB if assemblies are large or a local model shares the machine. Dassault’s published floor is 16 GB, with 32 GB recommended, before you add the agent.
When should we stop and call a manufacturer?
When the sandbox part needs a real process: tool access, draft, resin or sheet metal, and a quote. Contact Techwall with the STEP, the drawing PDF, and the constraint list. An engineer replies within one business day with a scoped consultation.
Sources
- Dassault Systèmes, SOLIDWORKS system requirements
- SOLIDWORKS, AI in SOLIDWORKS Design
- SOLIDWORKS news, AI Virtual Companions (AURA and LEO)
- Hawk Ridge Systems, How to Access the AI Virtual Companions
- eyfel/mcp-server-solidworks (SolidPilot)
- MCP_CAD deployment notes
- TechDraw AI, How to Connect Claude to SolidWorks (MCP, 2026)