Install
$ agentstack add mcp-just1step-solidworks-mcp ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
SolidWorks MCP Server
Language: English | [简体中文](./README.zh-CN.md)
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](../../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](./LICENSE).
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: just1step
- Source: just1step/solidworks-mcp
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.