Using Claude with SolidWorks involves more than asking an AI model to generate VBA macros, C# add-ins, or SOLIDWORKS API code. With a compatible Model Context Protocol (MCP) server, Claude can communicate with a running SolidWorks session through a local API or Windows COM bridge and work with structured CAD data.

Depending on the connector, Claude can inspect parts, assemblies, drawings, feature trees, configurations, mates, custom properties, and document metadata. It may also create drawing views, add dimensions and balloons, generate bills of materials, analyze assembly structures, run approved API operations, and export documentation. Community projects such as SolidWorks MCP demonstrate workflows for opening documents, generating standard drawing views, reading assembly information, and exporting drawings as PDFs.

Computer Use adds a visual layer to this connection. Claude can open the correct SolidWorks file, navigate the FeatureManager design tree, inspect a drawing sheet, read rebuild warnings, and verify that a generated result looks correct before it is saved.

This is not a native one-click SolidWorks feature. It requires a Windows environment, a compatible SolidWorks installation and license, an MCP server or API bridge, appropriate permissions, and a test copy of important CAD files.

What Can Claude Do With SolidWorks Through MCP and Computer Use?

When Claude is connected to SolidWorks through an MCP server, it can work with structured CAD information instead of treating the application as a simple desktop window. The exact capabilities depend on the connector, SolidWorks version, and API functions it exposes, but a compatible server can provide access to parts, assemblies, drawings, features, configurations, mates, and custom properties.

Claude can inspect an active document and determine whether it is a part, assembly, or drawing. It can read the FeatureManager design tree, identify sketches and bodies, list assembly components, inspect configurations, and report suppressed or unresolved items. It can also analyze metadata such as part numbers, materials, descriptions, revisions, and manufacturing properties.

Source: SOLIDWORKS Tech Blog – FeatureManager Assembly Tree

MCP can support more than read-only analysis. Some community implementations expose tools for creating drawing documents, adding standard views, importing model dimensions, inserting balloons, generating BOM tables, capturing model views, and exporting drawings as PDFs. These workflows build on the capabilities of the SOLIDWORKS API, rather than replacing the API itself.

Computer Use provides a different type of access. Claude can interact with the visible SolidWorks interface by opening a file, navigating the FeatureManager design tree, switching configurations, opening the PropertyManager, reading a rebuild warning, or checking the layout of a drawing sheet. This is especially useful when the MCP server does not expose a particular interface control or when the final result requires visual verification.

Used together, MCP can identify what needs attention, while Computer Use can open the relevant SolidWorks context and verify the visible result before Claude continues.

MCP vs. Computer Use: Which SolidWorks Connection Should You Use?

MCP and Computer Use provide different ways for Claude to work with SolidWorks. MCP is designed for structured communication with the SolidWorks API or COM bridge, while Computer Use allows Claude to interact with the visible SolidWorks interface. The most reliable workflows use each method for the type of task it handles best.

MCP is the stronger choice when Claude needs to inspect or process structured CAD information. A SolidWorks connector may expose tools for reading feature trees, configurations, components, mates, custom properties, drawing views, and document metadata. It can also perform repeatable operations such as creating standard drawing views, adding annotations, generating BOM tables, or exporting approved documents.

This approach is useful when consistency matters. For example, Claude can inspect every component in an assembly, identify suppressed or unresolved references, and group the results by configuration. It can also compare custom properties across multiple files without manually opening each document. These capabilities follow the general purpose of MCP: providing AI applications with standardized access to external tools and data.

Computer Use is more appropriate when the task depends on SolidWorks’ interface or visual output. Claude can open a drawing sheet, select a feature in the FeatureManager tree, switch to a configuration, inspect a PropertyManager panel, read a rebuild warning, or confirm that dimensions and balloons are positioned correctly. It can also operate menus and dialogs that the MCP server does not expose.

Source: CodeStack – Fix or Float Components Using the SOLIDWORKS API

A practical rule is simple: use MCP to query CAD data, analyze documents, run API operations, and create repeatable results. Use Computer Use to navigate SolidWorks, inspect visual context, operate interface-only controls, and verify drawings or model views. Use both when structured analysis must be followed by visual confirmation.

For example, Claude could use MCP to find parts with missing material or revision properties. It could then open a representative part with Computer Use, display the Custom Properties panel, and confirm that the result refers to the correct document. Only after approval should Claude update the affected files.

How Do You Connect Claude to a SolidWorks MCP Server?

Connecting Claude to SolidWorks requires a bridge between the AI client and the running SolidWorks application. Most available integrations use a local server that communicates with SolidWorks through Windows COM, pywin32, or the SOLIDWORKS API. Claude sends a tool request to the MCP server, the server translates it into an API operation, and SolidWorks returns structured information or performs an approved action.

The architecture usually looks like this:

The MCP server does not replace SolidWorks or automatically expose every feature. It provides a defined set of tools. One implementation may focus on drawings and PDF exports, while another may support parts, sketches, feature creation, assemblies, configurations, or custom properties. Before installing one, check its supported SolidWorks versions and operating requirements.

Source: The Ultimate Guide to Model Context Protocol

A typical setup includes:

• A Windows computer

• A compatible SolidWorks installation and license

• Access to the SOLIDWORKS API

• A SolidWorks MCP server or local bridge

• Python and pywin32, if required by the connector

• Claude Code or Claude Desktop with MCP support

• A test part, assembly, or drawing

• A backup copy of important CAD files

Most COM-based integrations require SolidWorks to be installed on the same Windows host as the MCP server. Some servers can be reached over a local network, but the SolidWorks application and its API bridge still need to run on the Windows machine where the CAD files are opened.

Basic Connection Process

Start by opening SolidWorks with a non-critical test document. Then download or clone a compatible MCP server, create its required Python environment, install the dependencies, and start the server on the SolidWorks host.

A community project such as SolidWorks MCP documents an HTTP-based setup. A Claude Code connection may look similar to this:

claude mcp add --transport http solidworks http://<sw-host>

claude mcp add --transport http solidworks http://<sw-host>

Other implementations use a local Python process:

The exact command, server name, transport, and file path depend on the implementation. Claude’s MCP configuration documentation covers local servers, HTTP servers, project scopes, user scopes, and commands such as claude mcp list and /mcp.

After registering the server, restart Claude if necessary and verify that the SolidWorks tools are available. Begin with a read-only request:

“Inspect the active SolidWorks document and report whether it is a part, assembly, or drawing. Do not modify anything.”

If Claude returns information from the open document, test a more specific query:

“List the top-level components in the active assembly and report their configurations and suppression states.”

Only after these checks should you try creating drawing views, running a macro, changing a property, or exporting a PDF. Save a separate version of the file before approving any operation that can modify the design.

How Do You Use Claude Computer Use With SolidWorks?

Computer Use allows Claude to interact with SolidWorks through its visible interface. Instead of depending only on MCP tools, Claude can observe the current SolidWorks window, identify the active document and configuration, and perform actions such as clicking, typing, selecting, opening panels, or switching views.

A reliable SolidWorks workflow follows an inspect–act–verify loop:

1. Claude observes the SolidWorks interface.

2. It confirms the active part, assembly, drawing, or configuration.

3. It identifies the required interface action.

4. It performs a click, keyboard shortcut, menu command, or text entry.

5. SolidWorks displays a new state.

6. Claude checks the updated feature tree, viewport, dialog, or drawing sheet.

7. It stops or continues based on the verified result.

This is useful when the operation depends on visual context. For example, MCP may identify a drawing that contains the required views, but Computer Use can open the sheet and check whether the views overlap, whether dimensions are readable, and whether balloons are positioned correctly. Similarly, MCP may return a feature or component name, while Computer Use can select it in the FeatureManager design tree and show its properties.

You can give Claude a narrowly defined instruction such as:

“Open the active drawing, inspect the sheet layout, and identify any dimensions or balloons that overlap model geometry. Do not move or delete anything.”

Other useful interface tasks include opening the ConfigurationManager, switching to a different configuration, expanding a feature tree, opening a sketch, checking rebuild warnings, changing model orientation, reviewing a section view, or opening the PDF export dialog.

Computer Use should not be treated as unrestricted control of the CAD workstation. Confirm that the correct SolidWorks document is open before each workflow. Require approval before Claude edits sketches, suppresses features, replaces assembly components, changes configurations, overwrites files, or exports design data. If SolidWorks displays an unexpected warning, rebuild error, save prompt, or different document, Claude should stop and request review.

Precise mouse-based operations, such as dragging sketch entities or positioning dimensions by a few pixels, can be fragile. Whenever possible, use MCP or the SOLIDWORKS API for deterministic changes, and use Computer Use to navigate the interface and visually verify the result. This follows Anthropic’s guidance to provide AI agents with tools that can verify UI work after an action.

What SolidWorks Workflows Can You Automate With Claude?

The most useful SolidWorks workflows combine MCP for structured CAD operations with Computer Use for visual inspection. Claude can query a part or assembly, determine what needs attention, propose a controlled action, and then use the SolidWorks interface to verify the result before saving or exporting the file.

Part and Feature Tree Inspection

Claude can inspect the active part’s feature tree and explain the modeling sequence. It can identify sketches, extrusions, cuts, fillets, chamfers, patterns, reference geometry, bodies, and dependencies. This is useful when an engineer inherits a part created by someone else or needs to understand which features are most likely to fail during a rebuild.

A suitable prompt might be:

“Inspect this part’s feature tree and explain the modeling sequence, dependencies, and features most likely to fail during rebuild.”

MCP can return the feature information as structured data, while Computer Use can select representative features in the FeatureManager design tree and open their PropertyManager panels for visual confirmation.

Source: Introduction to SolidWorks – Major User Interface Components

Assembly Structure and Mate Review

For assemblies, Claude can list top-level components, configurations, suppression states, and mates when the MCP connector exposes assembly-analysis tools. It can identify unresolved references, missing components, or components that are suppressed in one configuration but active in another.

Computer Use can open the assembly, expand the component tree, and inspect the model view to verify that the reported components are positioned as expected. This is helpful before issuing a revision or sharing the assembly with another team.

Claude could begin with:

“Read the active assembly structure and list components that are suppressed, unresolved, or missing references. Do not modify the assembly.”

Source: CAE1000 Assembly Tutorial

Drawing Creation and Documentation

Several community SolidWorks MCP implementations focus on drawing automation. The documented capabilities of SolidWorks MCP include creating a drawing from a template, adding standard views, inserting section and detail views, importing model dimensions, adding linear or radial dimensions, placing balloons, inserting a BOM table, and exporting the result as a PDF.

A controlled drawing workflow could follow this sequence:

1. Open a selected part or assembly.

2. Confirm the correct configuration.

3. Create a drawing from an approved template.

4. Add first-angle or third-angle standard views.

5. Insert model dimensions and annotations.

6. Add a BOM and balloons if the document is an assembly.

7. Open the drawing with Computer Use.

8. Check view overlap, annotation readability, and sheet scale.

9. Ask for approval.

10. Export the final drawing as a PDF.

MCP is useful for repeating the same drawing process across multiple parts. Computer Use adds the visual check that structured API output cannot provide by itself.

Source: SOLIDWORKS – Drawing Enhancements

Custom Properties and Metadata

Claude can inspect properties such as part numbers, descriptions, revisions, materials, weights, project identifiers, and manufacturing notes. It can compare these values across files or identify documents with missing metadata.

Computer Use can then open the Custom Properties interface and confirm that the correct document and configuration are selected before any values are changed. This is important because a property update may affect title blocks, BOM tables, PDM records, or downstream manufacturing documents.

Source: Linking a Revision Number to a Property in SolidWorks

Configuration and Design Variant Review

SolidWorks configurations allow different versions of a part or assembly to exist within the same document. Claude can compare configuration-specific dimensions, suppression states, component references, materials, and custom properties when the MCP server exposes them.

Computer Use can switch between configurations and visually confirm that the expected geometry appears. This is useful for identifying variants that share a common model but differ in size, component selection, or feature state.

Source: SolidWorks Configurations for Parts and Assembly Modeling

Rebuild Error Triage

Claude can help investigate rebuild problems by reading warnings, identifying failed features, tracing dependent sketches, and suggesting possible repair strategies. It can also generate an API or macro-based correction for review.

However, a repair should not be applied automatically to a production model. Changing one feature can affect dependent sketches, assemblies, configurations, and drawings. The safer workflow is to analyze the error, create a proposed fix, test it on a copy, rebuild the affected configurations, and compare the result visually.

Source: SOLIDWORKS Blog – Setting Up Bill of Materials

Documentation and Export Pipeline

Claude can also coordinate a repeatable documentation process:

“Open the approved assembly, confirm configuration Default, create the drawing using the company template, add standard views and a BOM, show me the result for review, and export a PDF only after approval.”

This type of workflow combines MCP’s repeatability with Computer Use’s visual verification. It is especially useful when teams need consistent drawing outputs without giving Claude unrestricted permission to modify design files.

How Do You Use MCP and Computer Use Safely With SolidWorks?

Connecting Claude to SolidWorks gives an AI system access to valuable design data and, depending on the MCP server, the ability to perform changes. The safest approach is to treat Claude as a controlled assistant rather than giving it unrestricted access to production CAD files.

Start with a copy of the part, assembly, or drawing. Use versioned filenames and keep the original file unchanged until the workflow has been reviewed. If the file is managed through PDM, confirm whether it is checked out, locked, or connected to a revision workflow before Claude attempts to save it.

Begin with read-only requests. Claude should first identify the active document, configuration, units, file path, and current state. A useful sequence is:

User approval should be required before Claude:

• Edits sketches or dimensions

• Suppresses or deletes features

• Replaces assembly components

• Changes configurations

• Updates custom properties across multiple files

• Overwrites an existing drawing

• Saves or closes a document

• Exports confidential design data

This approval step is particularly important for Computer Use because an incorrect click can select a different feature, configuration, or file than intended. Claude should stop if SolidWorks displays an unexpected warning, rebuild error, save prompt, or different document.

The Windows execution environment also matters. Many SolidWorks MCP servers rely on COM or pywin32. The MCP server and SolidWorks must run on a compatible Windows host, and some integrations require Claude and SolidWorks to use matching administrator privileges. The HarrierPigeon SolidWorks MCP project documents this type of COM and elevation requirement.

For additional protection, restrict the MCP server to the folders it needs, avoid broad write permissions, and log important operations. After every approved modification, rebuild the affected configurations, inspect the feature tree, compare the model or drawing with the previous version, and save a new revision rather than silently replacing the source file.

Run SolidWorks and Claude Together on Vagon Cloud Computer

SolidWorks automation depends heavily on the environment in which the application, MCP server, and CAD files run. A local workstation may work well for one user, but teams often need a persistent Windows computer where SolidWorks, Claude, the MCP bridge, and its dependencies remain configured between sessions. A Vagon Cloud Computer can provide this type of dedicated workspace.

You can install SolidWorks on the Windows cloud computer, configure Claude Code or Claude Desktop, and run the SolidWorks MCP server on the same machine. Python, pywin32, API dependencies, project files, templates, and export folders can remain available in one environment instead of being rebuilt each time.

Performance is important for both MCP and Computer Use workflows. CPU and RAM affect assembly loading, rebuilds, configuration changes, and API operations. GPU performance matters when Claude needs to inspect a complex 3D viewport, shaded model, section view, or drawing preview. A stable remote connection also helps Computer Use interpret the SolidWorks interface and interact with dialogs more reliably.

A typical Vagon setup might include:

This setup can be useful for repeatable drawing generation, assembly inspection, metadata review, and PDF export workflows. It also makes it easier to keep the MCP server and SolidWorks version consistent across repeated tasks.

Vagon does not add a native Claude–SolidWorks integration. You still need a valid SolidWorks license, a compatible MCP server, the correct Windows configuration, and permission to access any PDM system or network storage. Production files should remain protected with backups, version control, and approval-based workflows.

For teams, the main advantage is a persistent and performance-oriented environment where the entire SolidWorks–Claude workflow can be configured once and reused when needed.

FAQs

Can Claude directly control SolidWorks?

Claude can interact with SolidWorks when an MCP server or automation bridge exposes supported tools. It is not a native, one-click SolidWorks feature. The available controls depend on the MCP server, SolidWorks version, and API functions it provides.

Is there an official SolidWorks MCP server?

Most available SolidWorks MCP solutions are community-built. They typically use the SOLIDWORKS API, Windows COM, or pywin32 to expose selected SolidWorks capabilities to Claude.

Can Claude read SolidWorks parts and assemblies?

Depending on the connector, Claude may inspect active documents, feature trees, assembly components, configurations, mates, suppression states, and custom properties.

Can Claude create SolidWorks drawings?

Some MCP servers expose tools for creating drawing documents, adding standard views, inserting dimensions and balloons, generating BOM tables, and exporting drawings as PDFs. These capabilities are connector-dependent.

What is Computer Use useful for in SolidWorks?

Computer Use is useful for opening files, navigating the FeatureManager tree, switching configurations, checking PropertyManager panels, reading rebuild warnings, and visually verifying models or drawings.

Can Claude edit SolidWorks sketches?

It may be possible through API tools or Computer Use, but precise mouse-based sketch edits can be fragile. Test changes on a copy and require approval before modifying dimensions, constraints, or geometry.

Can Claude run SolidWorks macros?

If the MCP server exposes macro or API execution, Claude may generate or run approved automation code. Review the code before execution, especially when it can modify or overwrite CAD files.

Does SolidWorks need to be installed on Windows?

Most COM-based integrations require SolidWorks to run on the same Windows machine as the MCP server. The exact network setup depends on the connector, but SolidWorks and its API bridge must be available to the server.

Is it safe to connect Claude to production CAD files?

Begin with read-only inspection, backups, restricted permissions, and a test copy. Claude should request approval before editing, saving, deleting, suppressing, replacing, or exporting design data.

Can SolidWorks and Claude run on Vagon?

Yes. A Vagon Cloud Computer can host SolidWorks, Claude, the MCP server, Python dependencies, and project files in a persistent Windows environment. A valid SolidWorks license and compatible connector are still required.

Does Claude replace the SolidWorks API?

No. The API remains the deterministic automation layer. MCP exposes selected API capabilities to Claude, while Computer Use adds interface-level control and visual verification.

Can Claude repair failed SolidWorks features?

Claude can help diagnose rebuild errors, identify failed references, and propose API or macro-based corrections. Any repair should be tested on a copy because changing one feature can affect dependent sketches, features, configurations, assemblies, and drawings.