Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"solidworks": {
"env": {
"ADAPTER_TYPE": "winax-enhanced",
"SOLIDWORKS_PATH": "C:\\Program Files\\SOLIDWORKS Corp\\SOLIDWORKS"
},
"args": [
"C:/path/to/solidworks-mcp-server/dist/index.js"
],
"command": "node"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
The Most Intelligent Node.js-based SolidWorks Automation Solution
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.
Autonomous spec-to-product coding-agent CLI with an MCP server exposing 34 tools over stdio.
97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server
App framework, testing framework, and inspector for MCP Apps.
MCP Security Weekly
Get CVE alerts and security updates for Solidworks Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
The Most Intelligent Node.js-based SolidWorks Automation Solution
🚀 87 Tools | 📦 4 Resources | 💡 5 Prompts | 🧠 Intelligent COM Bridge | ⚡ Dynamic Fallback | 🎯 100% Feature Coverage
🎉 New Release v1.0.0 - This is a complete redesign of the SolidWorks MCP Server with intelligent COM bridge architecture, comprehensive tool coverage, and production-ready features.
Problem Solved: Node.js COM bridges fail when calling SolidWorks methods with 13+ parameters. This affects critical features like extrusions, sweeps, and lofts.
Our Solution: Intelligent adapter architecture that automatically routes operations:
# Clone the repository
git clone git@github.com:jianzhichun/solidworks-mcp-server.git
cd solidworks-mcp-server
# Install dependencies (compiles winax for your system)
npm install
# Build TypeScript
npm run build
Add to your claude_desktop_config.json:
{
"mcpServers": {
"solidworks": {
"command": "node",
"args": ["C:/path/to/solidworks-mcp-server/dist/index.js"],
"env": {
"SOLIDWORKS_PATH": "C:\\Program Files\\SOLIDWORKS Corp\\SOLIDWORKS",
"ADAPTER_TYPE": "winax-enhanced"
}
}
}
}
| Tool Name | Input Parameters | Output | Description | Use Case | Workflow |
|---|---|---|---|---|---|
create_sketch | plane (Front/Top/Right/Custom), offset (number, default: 0), reverse (boolean, default: false), customPlane (optional object) | success, sketchName, plane, offset, message | Create a new sketch on a specified plane or face | Initialize sketch for feature creation | 1. Select plane/face 2. Create sketch 3. Return sketch name |
edit_sketch | sketchName | success, sketchName, message | Enter sketch edit mode for an existing sketch | Modify existing sketch geometry | 1. Find sketch by name 2. Activate sketch 3. Return status |
exit_sketch | rebuild (boolean) | success, message | Exit sketch edit mode and optionally rebuild | Complete sketch editing | 1. Exit sketch 2. Optionally rebuild model |
get_sketch_context | maxFeatures (optional, default: 5) | hasModel, modelName, modelType, activeSketch, recentSketchFeatures | Get current model and sketch context for diagnostics | Debug sketch operations | 1. Get active model 2. Get active sketch 3. Return context |
sketch_line | start ({x, y, z}), end ({x, y, z}), construction (boolean, default: false) | success, message, position | Draw a line in the active sketch | Add line geometry | 1. Validate sketch active 2. Create line from points 3. Return entity info |
sketch_centerline | start ({x, |