mcp-server-solidworks — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor exact implementation activity, MCP interface, permission and setup changes.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

SolidWorks CAD operations

What we know

This MCP server integrates with SolidWorks API and structuring it into Claude-compatible context streams. Public Radar listing describes capability; verify precise runtime setup and privilege boundaries upstream.

Maintenance / activity evidence

GitHub exact repo pushed_at 2026-10-07T09:46:11Z

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
CAD API can modify engineering design files; limit automation to copied projects. Reported action classes: model/part changes. Complete write authority is not verified.
Refer to first-party setup documentation; do not infer authorization from package existence.
Sensitive access: CAD assemblies and design files

CAD API can modify engineering design files; limit automation to copied projects.
Public tracking suitability is not an installation safety audit.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

382 repository stars

Stars observed Oct 10, 2026.

Repository total for eyfel/mcp-server-solidworks.

All limitations / Review context

Has mcp-server-solidworks changed its documented MCP interface, authentication or privilege boundaries, and does it merit promotion?

Limited editorial listing; known permission implications disclosed, no independently established publication blocker.

CAD API can modify engineering design files; limit automation to copied projects.
Public tracking suitability is not an installation safety audit.
Refer to first-party setup documentation; do not infer authorization from package existence.
CAD assemblies and design files
Reviewed write actions: model/part changes
Sensitive access: CAD assemblies and design files
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Upstream credential and permission scopes must be validated before runtime use.
Precise setup/auth/permissions not verified
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted.
Exact GitHub pushed_at 2026-10-07T09:46:11Z

Original activity observations

GitHub exact repo pushed_at 2026-10-07T09:46:11Z

Technical identity

github.com/eyfel/mcp-server-solidworks

Exact implementation source: https://github.com/eyfel/mcp-server-solidworks ↗
Reviewed resource type: MCP Server
Repository identity: eyfel/mcp-server-solidworks

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

GitHub repository ↗
eyfel/mcp-server-solidworks
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 13, 2026.

Additional setup details required — see the specific gaps below.

Warning

SolidWorks automation can modify CAD designs; use non-production model.
Multiple publisher-documented README steps combined as an ordered excerpt; not a verbatim single publisher code block.
Absolute Windows paths are user-specific placeholders instead of publisher-machine paths. Replace the supplied illustrative path/credential placeholders with your own settings.
The SolidWorks execution backend is separate; stop it only if it is dedicated to this install. Keep CAD project data and SolidWorks intact.
Exact vendor-specific credential revoke procedure not established from checked official Setup documentation; may be external or not applicable. Do not invent.
Absolute Windows paths are user-specific placeholders instead of publisher-machine paths. Replace the supplied credential/path placeholders privately; use only the named configuration schema.
MCP100 client-scope note: this Claude Code CLI example applies only to that client and the exact registered name in the command. Desktop, Cursor and other clients use their own configuration; do not run it for a differently named entry.

Install / connect
Publisher instructions
Publisher-specific setup path. Follow prerequisites, then register or connect to your MCP host.
publisher documented install or connect · Publisher instructions · Review before use
```
cd adapters/claude
pip install -r requirements.txt
python server.py
```
Configure / authenticate
Publisher instructions
First build/run execution/SolidworksExecution on Windows with SolidWorks 2026, then configure client to spawn absolute adapters/claude/server.py.
Advanced configuration · claude desktop json · Publisher instructions
claude desktop json · Publisher instructions
{ "mcpServers": { "SolidPilot": { "args": [ "C:\\PATH\\TO\\SOLIDPILOT\\adapters\\claude\\server.py" ], "command": "C:\\PATH\\TO\\PYTHON\\python.exe", "cwd": "C:\\PATH\\TO\\SOLIDPILOT\\adapters\\claude" } } }
Check connection
Suggested check
After execution layer is listening at http://localhost:5000, confirm adapter and client tools are discoverable without editing a SolidWorks file.
Remove / uninstall / revoke
MCP100 setup guide
Remove SolidPilot MCP client entry, terminate Python adapter and SolidworksExecution processes; leave SolidWorks installed.
MCP100 client-scope guidance: each CLI removal example targets only its named client and exact registered entry. Package names, Desktop/Cursor configuration keys and Codex/Claude registration names may differ; use the entry you actually registered. Client removal does not revoke provider credentials.
claude mcp remove SolidPilot

Official Documentation & Sources

What it does

This MCP server integrates with SolidWorks API and structuring it into Claude-compatible context streams. Public Radar listing describes capability; verify precise runtime setup and privilege boundaries upstream.

Capability: Developer Tools
Resource type: MCP Server
Industry: Manufacturing & Industrial
Best fit: SolidWorks CAD operations

Representative uses

SolidWorks CAD operations

Limitations

CAD API can modify engineering design files; limit automation to copied projects.
Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted.
Exact GitHub pushed_at 2026-10-07T09:46:11Z

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Refer to first-party setup documentation; do not infer authorization from package existence.
Permissions: CAD API can modify engineering design files; limit automation to copied projects.
Data handling: CAD assemblies and design files
Cost: Provider or usage fees possible; verify current pricing
Risk and cautions: CAD API can modify engineering design files; limit automation to copied projects.

Access scope and cautions

Write actions: Not verified model/part changes
Sensitive access: CAD assemblies and design files
Risk level: high
Security notes: CAD API can modify engineering design files; limit automation to copied projects. Public tracking suitability is not an installation safety audit.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T03:38:00Z. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: SolidWorks CAD operations.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Installation command omitted unless verified or clearly package-specific; do not infer npx/uvx entrypoints. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Refer to first-party setup documentation; do not infer authorization from package existence.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: model/part changes. Recorded permission context: CAD API can modify engineering design files; limit automation to copied projects.

What data-handling boundary should I consider?

CAD assemblies and design files Recorded sensitive-access context: CAD assemblies and design files.

What limitations and risks should I check before use?

CAD API can modify engineering design files; limit automation to copied projects. Some integration/runtime instructions are not confirmed from a first-party install guide and therefore intentionally omitted. Exact GitHub pushed_at 2026-10-07T09:46:11Z. Public tracking suitability is not an installation safety audit. Upstream credential and permission scopes must be validated before runtime use.