原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

SolidWorks MCP

作者:andrewbartels1版本 1.5.0i★ –i在你的电脑上运行
注册名称io.github.andrewbartels1/solidworks-mcp-python

安装

概览

作者提供的说明(英文原文)

Drive SolidWorks from AI agents: parts, assemblies, drawings and export over the COM API.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 其他

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 注册中心没有列出需要填写的密钥。

你需要

  • PyPI已安装 Python 的 uv(用于 uvx 命令)

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "solidworks-python": {
      "command": "uvx",
      "args": [
        "solidworks-mcp-python"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add solidworks-python -- uvx solidworks-mcp-python

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "solidworks-python": {
      "command": "uvx",
      "args": [
        "solidworks-mcp-python"
      ]
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "solidworks-python": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "solidworks-mcp-python"
      ]
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 andrewbartels1 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 32417 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 32417 个服务器的 88% 更新
  • 基础检查结果等于或优于此分类中其他 32417 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

SolidWorks MCP 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(1.5.0)于4天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, FOGA node

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者:formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新
安装

Remote Desktop Commander

作者:desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新
安装

FOGA node

作者:garyyang-finchip

A Finch OG Agent cell as an MCP server: read the world, dry-run and take ERC-8414 tenders by policy.

电脑或云端今天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

SolidWorks CAD Assistant & MCP Server

Languages: English | Español

Python MCP server for SolidWorks automation with 154 tools, plus an optional agent/prompt-testing layer for AI-assisted workflows.

See it work

Make a 100 x 50 x 10 mm AISI 1020 mounting plate with four M5 clearance holes, 10 mm in from each edge, and draw it fully dimensioned. Stack two of them 10 mm apart, check the result, and draw the assembly with a BOM.

The 58 tool calls an agent made from that prompt, run against SolidWorks 2026 through the same MCP tools a client calls, and recorded (sped up five times). Each result is checked against a hand calculation: the plate's volume and mass, the 10 mm gap and the BOM quantity. This is a replay of the calls, not a recorded model session.

Note: the demo is not perfect, and is not the most efficient way to get this result. The run pauses after each call so it can be read, and the calls are chosen to show what the tools can do: every sketch dimension is added one at a time, and the mate distance is stepped down only so the plates are seen coming together.

The walkthrough in the docs has the agent's plan and every call with its arguments. Run it yourself with the README demo; the calls are also in plate_stack_calls.json.

The 58 tool calls

  1. Sketch (24 calls): create_sketch on Top; four add_line for the 100 x 50 outline; add_circle for each Ø5.5 hole; add_sketch_dimension for the 100, the 50, one Ø5.5 and each hole 10 mm from two edges; add_sketch_constraint making the other three holes equal; exit_sketch
  2. Check and extrude: check_sketch_fully_defined, create_extrusion 10 mm (+49 049.7 mm³ read back)
  3. Material and check: list_model_dimensions (finds the Ø5.5 by value), set_material AISI 1020, verify_model (volume, mass 0.3875 kg, size, 1 feature, 1 body)
  4. Plate drawing: generate_drawing_package PS-01 (A3, four views, every model dimension laid out with no overlaps, notes, title block, PDF), auto_center_marks
  5. GD&T: add_datum_tag A, B and C, then add_gtol ⊕ Ø0.2 Ⓜ A|B|C on the Ø5.5
  6. Assembly: insert_component twice, list_components, add_mate Front and Right coincident and Top planes 60 mm apart, set_dimension stepping that distance down to 20 mm (10 calls), verify_model (2 parts, 3 mates, no interference; the stack measures 30 mm, so the gap is 10 mm)
  7. Assembly drawing: set_custom_property Material, generate_drawing_package PS-02 with include_bom (the BOM above the isometric: Demo Plate, QTY 2), then the same datums and position frame

Overview

Tried it? Tell us what worked and what didn't in a feedback issue. Reports from real setups decide what gets fixed next.

This project focuses on practical SolidWorks automation with an AI-friendly loop:

  1. describe intent
  2. generate a plan
  3. execute MCP tools
  4. inspect results
  5. iterate

It includes:

  • core MCP runtime for SolidWorks tool execution
  • COM/VBA routing and adapter safety wrappers
  • tool coverage across modeling, sketching, drawing, analysis, export, automation, templates, and macros
  • optional agent orchestration/testing utilities under src/solidworks_mcp/agents/

Demos

Each GIF is a live test driving SolidWorks 2026 through the MCP tools, with the call and its result captioned beneath. Click one to see what it checks, a prompt that asks for it, and its tool calls.

verify_model passes a block and names what is wrong

An assembly: parts, mates and interference

A cut reports the volume it removed

A revolve reports the volume it added

A round part's size is exact

Reading the model keeps the selection

A full drawing package from one call

Setting the sheet scale

A BOM on an assembly drawing

Each model dimension shown once

Clearing every overlap

Material and mass

Listing dimensions and measuring a face

Flat pattern of a sheet-metal part

Custom properties

[See every demo in the docs](https://andrewbartels1.github.io/SolidworksMCP-python/demos/): what each one shows, its prompt, every tool call with its arguments (all 58 for the demo at the top), and how to run them yourself.

Supported Today

  • Windows + SolidWorks COM automation for the main CAD lifecycle.
  • Tested on SolidWorks 2026. Earlier versions may work but are untested; if you try one, please open an issue with what worked.
  • Modeling, sketching, drawing, analysis, export, automation, templates, and macro tools.

Not Yet / Simulated

  • Mock adapter output is simulated and should not be treated as engineering truth.
  • Live 3D viewport streaming in a UI.
  • Checkpoint-level interference validation.
  • Simple simulation and fluid workflows
  • Simple Topology Optimization via SimulationXpress etc.

Install

You need Windows 10 or 11 and SolidWorks (opened at least once). In PowerShell, install uv, then open a new PowerShell window and run setup:

powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

uvx solidworks-mcp-python setup

uv fetches Python 3.13 and the server from PyPI by itself; nothing to clone. The guided setup then:

  1. finds your SolidWorks version and the MCP clients on your PC: Claude Desktop, Claude Code, VS Code, Cursor and LM Studio;
  2. lets you pick which clients to connect;
  3. starts the server once to check that it lists its tools (in mock mode, so SolidWorks isn't touched);
  4. adds a solidworks entry to each client you picked, then tells you what to restart.

Nothing needs a login or an API key, and the server runs only on your PC. Setup changes only the solidworks entry in each client's config. It backs the file up first and never shows or changes your other servers. Other entries that start this server the old way (run-mcp.ps1 and the like) are offered for removal, so tools don't load twice.

To check it worked: open SolidWorks, restart your client, and ask *"What model is open in SolidWorks?"*

The package is solidworks-mcp-python. uvx solidworks-mcp installs a different project. To work on the server itself, install from a clone. More fixes are in Troubleshooting.

Connect your client

Run

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx