About Solidworks MCP
Solidworks MCP is an MCP server in the Blockchain category: mCP server for SolidWorks on Windows — open and edit parts/assemblies, create geometry, mates, measure, rebuild, export, and more via a TypeScript front door and .NET COM worker. It has been installed 0 times through Conduid.
Install
git clone https://github.com/just1step/solidworks-mcpThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Solidworks MCP
Powered by Claude · Grounded in docs
Security checks
- ·README presentNot checked yet.
- ·License declaredNot checked yet.
- ·Tests presentNot checked yet.
- ·Dependencies pinnedNot checked yet.
- ·No dynamic code executionNot checked yet.
- ·Scoped permissionsNot checked yet.
README
SolidWorks MCP Server
Language: English | 简体中文
SolidWorks MCP Server exposes local SolidWorks automation as a Windows-only MCP server.
This project ships as a single user-facing executable: SolidWorksMcpApp.exe.
Demo

What It Is
SolidWorksMcpApp.exeis the only supported entrypoint.- The app runs a tray-based Hub that owns the shared SolidWorks COM/STA session.
- MCP clients connect through the same exe in
--proxymode. - The supported path is
client -> proxy -> hub -> MCP tools -> SolidWorks.
Requirements
- Windows 10/11 x64
- SolidWorks installed locally, with
SldWorks.Applicationavailable for COM activation - .NET 8 Runtime for source-adjacent app builds; the published release binary is packaged as a self-contained single exe
- An MCP client that supports stdio, such as VS Code or Claude Desktop
SolidWorks Version Support
| SolidWorks version | Support status | High-risk mutation workflows |
|---|---|---|
| 2024 | Certified | Enabled |
| 2025 | Targeted | Enabled |
| 2026 | Experimental | Blocked |
| Older than 2024 | Unsupported | Blocked |
| Newer than 2026 | Unsupported | Blocked |
Quick Start
- Download
SolidWorksMcpApp.exefrom Releases. - Start the exe and confirm the tray icon appears.
- Export client config from the tray menu.
- Add that config to your MCP client.
For local use and testing, do not start SolidWorksBridge directly.
Development
Build:
dotnet build app/SolidWorksMcpApp/SolidWorksMcpApp.csproj -c Release
Run non-integration tests:
dotnet test bridge/SolidWorksBridge.sln --configuration Release --filter "Category!=Integration"
Run SolidWorks integration tests through the real hub/proxy path:
scripts/test-integration.bat
Repository Layout
app/SolidWorksMcpApp/: tray app, Hub/Proxy host, MCP tool registration, packaging entrypointbridge/SolidWorksBridge/: SolidWorks COM-facing services and workflow logicbridge/SolidWorksBridge.Tests/: unit and integration tests
Logs
If a tool call fails, check the logs/ directory next to the exe.
License
This project is licensed under the MIT License.
README mirrored from the source repository 20 days ago. The original is authoritative.