SolidWorks MCP PRO
Related Servers
Alternatives to SolidWorks MCP PRO
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables an AI assistant to drive an already-running SOLIDWORKS session over its COM API, so it can build sketches, solid features, reference geometry, assemblies, mates, and engineering drawings, then inspect the result through topology listings, mass properties, measurements, and screenshots returned as images.1Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to drive SOLIDWORKS from natural-language design intent, building and inspecting fully defined parts, assemblies, and drawings while measuring results against requested dimensions and properties.1MIT
- FlicenseBqualityCmaintenanceEnables AI agents to drive SolidWorks for parametric modelling, aerospace part generation, sheet metal, weldments, assemblies, drawings, simulation, inspection, and file export. It provides approval-gated operations, verification tools, and journaling for safe, recoverable design automation.94-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents such as Claude to drive SolidWorks through its COM API using natural language, creating parts and assemblies, sketching geometry, and adding features without clicking menus. Also supports running arbitrary API scripts and verifying results through model reports, rendered views, interference checks, and exports.1MIT
- AlicenseBqualityAmaintenanceEnables an AI assistant to create and edit parts in a live SolidWorks session through the COM API, with sketching, extruding, cutting, measuring, and exporting commands.692MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI (e.g., Claude) to control SolidWorks via natural language, automating part creation, sketching, and feature operations through the Model Context Protocol.1MIT
TDQS
Scored across 123 tools
Many tools have heavily overlapping purposes: add_extruded_profile vs add_extruded_profile_on_plane vs add_extruded_profile_on_face vs extrude_sketch, add_hole vs add_counterbore_hole vs add_hole_wizard vs add_hole_on_face, cut_profile vs cut_sketch, add_swept_pipe vs add_swept_profile vs swept_region, and a dense pro_visualize_* / preview / shot-pack cluster. Descriptions are repetitive boilerplate ('...through the independent native SOLIDWORKS engine') that does little to differentiate similar tools. An agent would frequently misselect among near-duplicate geometry and rendering tools.
Most tools follow a snake_case verb_noun pattern, but there is a clear split between native tools and a separate 'pro_' prefixed family, plus several noun-first or bare names (screenshot, export, rebuild, swept_region, loft_sketches). The convention is readable but not uniform across the whole set.
123 tools is far beyond any reasonable agent-facing surface, and the count is inflated by many marginal variants (on_plane/on_face counterparts, hole variants, numerous pro_visualize_* entries). This is an extreme mismatch for practical tool selection.
Coverage is very broad: sketching, solids, features, assemblies, mates, drawings, export, rendering, validation, diagnostics, and operation polling are all present. Minor gaps are hard to identify given the surface, but the lifecycle is largely covered with few dead ends.