SolidWorks MCP

io.github.andrewbartels1Published by GitHub account andrewbartels1v1.5.0Updated Nov 3, 2026

Drive SolidWorks from AI agents: parts, assemblies, drawings and export over the COM API.

VerifiedSTDIODesktop onlyAI & ML

Overview

SolidWorks's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open SolidWorks MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

SolidWorks CAD Assistant & MCP Server

Languages: English | Español

[Python 3.13+] [License: MIT] [Windows] [SolidWorks] [Coverage]

Python MCP server for SolidWorks automation with 154 tools, plus an optional agent/prompt-testing layer for AI-assisted workflows.

See it work

Make a 100 x 50 x 10 mm AISI 1020 mounting plate with four M5 clearance holes, 10 mm in from each edge, and draw it fully dimensioned. Stack two of them 10 mm apart, check the result, and draw the assembly with a BOM.

[A fully dimensioned plate, its drawing with GD&T, two plates mated 10 mm apart and the assembly drawing with a BOM, built in SolidWorks through the MCP tools]

The 58 tool calls an agent made from that prompt, run against SolidWorks 2026 through the same MCP tools a client calls, and recorded (sped up five times). Each result is checked against a hand calculation: the plate's volume and mass, the 10 mm gap and the BOM quantity. This is a replay of the calls, not a recorded model session.

Note: the demo is not perfect, and is not the most efficient way to get this result. The run pauses after each call so it can be read, and the calls are chosen to show what the tools can do: every sketch dimension is added one at a time, and the mate distance is stepped down only so the plates are seen coming together.

The walkthrough in the docs has the agent's plan and every call with its arguments. Run it yourself with the README demo; the calls are also in plate_stack_calls.json.

The 58 tool calls
  1. Sketch (24 calls): create_sketch on Top; four add_line for the 100 x 50 outline; add_circle for each Ø5.5 hole; add_sketch_dimension for the 100, the 50, one Ø5.5 and each hole 10 mm from two edges; add_sketch_constraint making the other three holes equal; exit_sketch
  2. Check and extrude: check_sketch_fully_defined, create_extrusion 10 mm (+49 049.7 mm³ read back)
  3. Material and check: list_model_dimensions (finds the Ø5.5 by value), set_material AISI 1020, verify_model (volume, mass 0.3875 kg, size, 1 feature, 1 body)
  4. Plate drawing: generate_drawing_package PS-01 (A3, four views, every model dimension laid out with no overlaps, notes, title block, PDF), auto_center_marks
  5. GD&T: add_datum_tag A, B and C, then add_gtol ⊕ Ø0.2 Ⓜ A|B|C on the Ø5.5
  6. Assembly: insert_component twice, list_components, add_mate Front and Right coincident and Top planes 60 mm apart, set_dimension stepping that distance down to 20 mm (10 calls), verify_model (2 parts, 3 mates, no interference; the stack measures 30 mm, so the gap is 10 mm)
  7. Assembly drawing: set_custom_property Material, generate_drawing_package PS-02 with include_bom (the BOM above the isometric: Demo Plate, QTY 2), then the same datums and position frame

Overview

Tried it? Tell us what worked and what didn't in a feedback issue. Reports from real setups decide what gets fixed next.

This project focuses on practical SolidWorks automation with an AI-friendly loop:

  1. describe intent
  2. generate a plan
  3. execute MCP tools
  4. inspect results
  5. iterate

It includes:

  • core MCP runtime for SolidWorks tool execution
  • COM/VBA routing and adapter safety wrappers
  • tool coverage across modeling, sketching, drawing, analysis, export, automation, templates, and macros
  • optional agent orchestration/testing utilities under src/solidworks_mcp/agents/

Demos

Each GIF is a live test driving SolidWorks 2026 through the MCP tools, with the call and its result captioned beneath. Click one to see what it checks, a prompt that asks for it, and its tool calls.

[verify_model passes a block and names what is wrong]
verify_model passes a block and names what is wrong		[An assembly: parts, mates and interference]
An assembly: parts, mates and interference		[A cut reports the volume it removed]
A cut reports the volume it removed
[A revolve reports the volume it added]
A revolve reports the volume it added		[A round part's size is exact]
A round part's size is exact		[Reading the model keeps the selection]
Reading the model keeps the selection
[A full drawing package from one call]
A full drawing package from one call		[Setting the sheet scale]
Setting the sheet scale		[A BOM on an assembly drawing]
A BOM on an assembly drawing
[Each model dimension shown once]
Each model dimension shown once		[Clearing every overlap]
Clearing every overlap		[Material and mass]
Material and mass
[Listing dimensions and measuring a face]
Listing dimensions and measuring a face		[Flat pattern of a sheet-metal part]
Flat pattern of a sheet-metal part		[Custom properties]
Custom properties

See every demo in the docs: what each one shows, its prompt, every tool call with its arguments (all 58 for the demo at the top), and how to run them yourself.

Supported Today

  • Windows + SolidWorks COM automation for the main CAD lifecycle.
  • Tested on SolidWorks 2026. Earlier versions may work but are untested; if you try one, please open an issue with what worked.
  • Modeling, sketching, drawing, analysis, export, automation, templates, and macro tools.

Not Yet / Simulated

  • Mock adapter output is simulated and should not be treated as engineering truth.
  • Live 3D viewport streaming in a UI.
  • Checkpoint-level interference validation.
  • Simple simulation and fluid workflows
  • Simple Topology Optimization via SimulationXpress etc.

Install

You need Windows 10 or 11 and SolidWorks (opened at least once). In PowerShell, install uv, then open a new PowerShell window and run setup:

powershell
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"uvx solidworks-mcp-python setup

uv fetches Python 3.13 and the server from PyPI by itself; nothing to clone. The guided setup then:

  1. finds your SolidWorks version and the MCP clients on your PC: Claude Desktop, Claude Code, VS Code, Cursor and LM Studio;
  2. lets you pick which clients to connect;
  3. starts the server once to check that it lists its tools (in mock mode, so SolidWorks isn't touched);
  4. adds a solidworks entry to each client you picked, then tells you what to restart.

Nothing needs a login or an API key, and the server runs only on your PC. Setup changes only the solidworks entry in each client's config. It backs the file up first and never shows or changes your other servers. Other entries that start this server the old way (run-mcp.ps1 and the like) are offered for removal, so tools don't load twice.

To check it worked: open SolidWorks, restart your client, and ask "What model is open in SolidWorks?"

The package is solidworks-mcp-python. uvx solidworks-mcp installs a different project. To work on the server itself, install from a clone. More fixes are in Troubleshooting.

Connect your client

Run setup again whenever you want to add a client:

powershell
uvx solidworks-mcp-python setup
OptionWhat it does
--client claude-desktopConfigure one client without the list. Repeat it for several (claude-code, vscode, cursor, lmstudio).
--dry-runShow what would change, and change nothing.
--yesDon't ask: configure every client found.
--removeTake the solidworks entry out again.
--replace-oldRemove older entries for this server without asking.
--mockConfigure mock mode, which answers without SolidWorks (for trying the tools).
--year 2026The SolidWorks release to start the server with. Default: the newest installed.

To set up a client by hand instead, each one runs uvx solidworks-mcp-python --year 2026, with your SolidWorks year. --year names your installed SolidWorks release and is required for real SolidWorks; setup fills it in for you. It picks which SolidWorks API the lookup tools answer for. Without it, the server logs a warning and uses the newest installed release. If a client can't find uvx, use its full path, from (Get-Command uvx).Source.

Claude Desktop

Add this to claude_desktop_config.json, alongside anything already in it. Depending on how Claude Desktop was installed, the file is in one of:

  • %LOCALAPPDATA%\Claude-Data\claude_<id>\ (current releases)
  • %LOCALAPPDATA%\Packages\Claude_<id>\LocalCache\Roaming\Claude\
  • %APPDATA%\Claude\
json
{  "mcpServers": {    "solidworks": {      "command": "uvx",      "args": ["solidworks-mcp-python", "--year", "2026"]    }  }}

Quit Claude Desktop from the system tray (closing the window isn't enough) and reopen it. Settings > Developer should show solidworks as running.

Claude Code
powershell
claude mcp add --scope user solidworks -- uvx solidworks-mcp-python --year 2026

Run /mcp in a new session to check that solidworks is connected.

VS Code

Add this to %APPDATA%\Code\User\mcp.json:

json
{  "servers": {    "solidworks": {      "type": "stdio",      "command": "uvx",      "args": ["solidworks-mcp-python", "--year", "2026"]    }  }}

Run MCP: List Servers from the Command Palette and start solidworks. Its output should end with Discovered 154 tools (the count grows as tools are added).

LM Studio

Add this to %USERPROFILE%\.lmstudio\mcp.json:

json
{  "mcpServers": {    "solidworks": {      "command": "uvx",      "args": ["solidworks-mcp-python", "--year", "2026"]    }  }}

Restart LM Studio and enable solidworks in the Program tab.

For mock mode, which needs no SolidWorks, use "args": ["solidworks-mcp-python", "--mock"]. Linux and WSL work for the docs, the tests and mock mode, but not for driving SolidWorks.

Optional features (environment variables)

Set these in your client's env block for the server, or in the shell before starting it by hand. Every SOLIDWORKS_MCP_<FIELD> maps to the config field of the same name.

SolidWorks-as-Code session logging (off by default). Logs every adapter tool call to a local SQLite database, so a session can be replayed or exported as a runnable Python script (see docs/getting-started/solidworks-as-code.md).

VariableDefaultMeaning
SOLIDWORKS_MCP_SOC_LOGGING_ENABLEDfalseTurn logging on.
SOLIDWORKS_MCP_SOC_SESSION_ID(generated)Session name to log under. If unset while logging is on, a soc-YYYYMMDD-HHMMSS id is generated at startup.
SOLIDWORKS_MCP_SOC_DB_PATH.solidworks_mcp/agent_memory.sqlite3Override the database file.
powershell
$env:SOLIDWORKS_MCP_SOC_LOGGING_ENABLED = "true"$env:SOLIDWORKS_MCP_SOC_SESSION_ID = "my-bracket".\.venv\Scripts\solidworks-mcp.exe# ...work in your MCP client....\.venv\Scripts\python.exe -m solidworks_mcp.agents.soc_exporter my-bracket my_bracket.py

It works only with the circuit-breaker adapter wrapper (the default for real SolidWorks); the mock adapter does not log.

API docs index auto-refresh (on by default). The API-lookup tools (lookup_api_interface, lookup_api_method, find_related_api_members) and search_solidworks_api_help read a JSON index built by discover_solidworks_docs. When the index is older than the threshold, the next lookup rebuilds it.

VariableDefaultMeaning
SOLIDWORKS_MCP_DOCS_INDEX_AUTO_REFRESHtrueRebuild a stale index automatically. No-op without SolidWorks + win32com; a failed rebuild keeps serving the existing index.
SOLIDWORKS_MCP_DOCS_INDEX_MAX_AGE_DAYS21Age after which the index counts as stale.

Contributing

install.ps1 gives you an editable install, so code changes take effect the next time a client starts the server. For the development tools, install the extras:

powershell
.\.venv\Scripts\python.exe -m pip install -e ".[dev,test,docs]"

.\dev-commands.ps1 lists the common workflows:

  • dev-install: install or update the local dev environment
  • dev-test: run the standard test suite (the CI-safe subset)
  • dev-test-full: run the full suite, including smoke and integration paths
  • dev-lint and dev-format: lint checks and formatting
  • dev-docs-build, dev-docs-strict and dev-docs-audit: build the docs, build them failing on warnings, or write an audit report to .generated/docs

To mirror GitHub Actions CI locally (Ubuntu, the conda env from solidworks_mcp.yml, and make test), run .\scripts\run-ci-local.ps1. The first run builds the image; add -NoBuild to re-run tests without rebuilding.

Docs

Key docs sections:

Direct links:

License

MIT License. See LICENSE.

Source: README.md at commit 126beed

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.5.0LatestNov 3, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts