SOLIDWORKS MCP: CAD work from your AI assistant

Hunter BI has completed a SOLIDWORKS MCP project. The shared experience is that the client performs work from an AI assistant and reports improved productivity. No percentage, number of cases or time saving is published. Customer documents and delivered functionality are not disclosed, and no named customer testimonial is reproduced.

For your team, start with identifiable work: which information should be consulted, what outcome should be prepared and who checks it? This separates document assistance from a design-changing operation. The same general benefit can correspond to very different scopes, each requiring its own permissions, tests and approval responsibilities.

The project should begin with the vendor's API documentation for the installed SOLIDWORKS version. Identify supported interfaces for the required task rather than relying on undocumented behaviour or an example written for a different release. The linked guide is a reference point, not proof that a given operation is available in your configuration.

Distinguish SOLIDWORKS Design, additional modules and any PDM environment. Confirm licences, permissions, dependencies and execution requirements before advertising compatibility to users. The MCP connector exposes selected operations to the assistant; it does not imply unlimited access to all components or authorise every action supported by the underlying API.

Vendor reference: SOLIDWORKS API guide — version 2025

Reading document properties, preparing an assembly summary or performing a controlled export are possible scenarios to qualify. They are not asserted as features of the customer implementation cited above. For each, check that the available interface supplies the required information and that the output can be compared with an engineering-approved reference.

Avoid combining too many transformations in the first task. Describe the input document, expected fields, exclusions and output format. If a request has an ambiguous name or lacks a revision, ask for clarification. Silently choosing a file whose validity is unknown creates a design risk even when the operation itself executes successfully.

Acceptance tests must cover document context, not just the presence of an assistant response. Define file-selection rules, how properties are read and how units are displayed. Check how missing references, alternative configurations and unexpected revisions are reported. Adapt these checks to the actual operations in the agreed scope.

For a modification or export, identify the targets and destination before execution. Approval for one document state must not silently cover another. A competent reviewer examines the result after the action. MCP integration does not replace a design review, demonstrate conformity with an engineering standard or authorise a part to enter manufacture.

Compare representative tasks with and without the assistant workflow. Count preparation, search, inspection and correction time until the result is accepted. A quickly executed command followed by a lengthy verification may not improve the overall job. Track wrong-file or wrong-reference errors separately from wording problems.

Hunter BI's qualitative report is not an independent measurement. Agree a sample and acceptance criteria before the pilot. Released time may help the team handle work, but it does not automatically demonstrate a financial saving or improved mechanical quality. Keep conclusions limited to the tasks, documents and configurations actually evaluated, including the cases that failed.

The assistant needs an explicit access perimeter: authorised documents, available commands and actions requiring a human decision. Information sent to the model can be sensitive even when it consists only of names, properties or references. Project owners should know those flows and the traces retained by each service.

The operating package should record tested versions, dependencies, incident ownership and how to suspend the connector. Define a procedure for returning to an approved working state after an incident. Updates to SOLIDWORKS, an additional module or the assistant should trigger checks on affected operations before their continued availability is confirmed. Agree handover and maintenance responsibilities rather than presuming ongoing support.