MIT dsh/Codex plugin bundling two pinned upstream CAD MCP servers (242 AutoCAD tools, 66 SolidWorks tools, both behind search entry points) with a self-authored AutoCAD skill and a `deliver` gate — you get a verdict someone else can re-check, not an agent claiming success.
DSH integration
Native runtime
Author-claimed
Safety audit
Unaudited
Last verified
2026-11-20
License
MIT
01What can it help you accomplish?
Draw an ISO sheet or model a part on a live AutoCAD / SolidWorks session from a plain-language brief
Real files on disk — DXF/DWG drawings with title block and dimensions, SLDPRT/SLDASM parts and STEP exports — plus previews (8-step validator and screenshot on AutoCAD, four orthographic views on SolidWorks)
Mechanical designers and CAD engineers running dsh (or Codex) on a Windows workstation with AutoCAD and/or SolidWorks installed
Replace "the agent says it finished" with a verdict somebody else can check
`delivery.json` with one PASS / warn / FAIL line per check, a SHA-256 per file, and exit code 0 or 1
Teams that hand drawings to a reviewer or a shop and need machine-verifiable output
Hold the values written on a drawing to a standards table before it leaves the desk
`half` profile: fits, material grades, heat and surface treatment and the Ra series outside `lib/standards.json` fail, and so does a drawing with no material and no Ra
Drafting leads doing a first-pass review on their own drawings
02How to install into DeepSeek Harness
Prerequisites
- Windows 10/11 with AutoCAD and/or SolidWorks installed — the integration is COM automation
- Python ≥ 3.11
- Node ≥ 20 for the plugin and npm install routes
- dsh (DeepSeek Harness) or Codex; Git is optional, the installer falls back to a codeload zip
Installation steps
- 01
Add it as a dsh plugin: `dsh plugin --profile web add dsh-sw-cad` — package.json declares `dsh.bundle.patch`, so dsh loads `cordis.patch.yml` and inserts one row
$ dsh plugin --profile web add dsh-sw-cad
- 02
Or go global with npm: `npm install -g dsh-sw-cad`, then `dsh-sw-cad install` (same result, plus the CLI on PATH)
$ npm install -g dsh-sw-cad
- 03
Keep exactly one route — if the plugin is installed, leave `~/.dsh/cordis.patch.yml` at `[]`
- 04
Start AutoCAD / SolidWorks first, as the same user the agent runs as
Verify the integration
- `dsh-sw-cad doctor` — read-only, exits 1 when something is missing
- `dsh --profile headless --dump-config` — dsh sees both server rows
- `node bin\dsh-sw-cad.mjs serve solidworks` — JSON-RPC handshake, expects 3 entry tools
- `python patches\apply_patches.py --check` — read-only, exits 1 when an upstream patch drifted
03DSH integration and capability boundaries
Native dsh plugin bundle — `dsh plugin --profile web add dsh-sw-cad` loads its `cordis.patch.yml` row, resolves paths, installs the pinned upstream servers and registers both CAD MCP clients with absolute paths
AutoCAD MCP server — 242 tools behind one search entry
`search_tools` with a keyword, then `call_tool` with flat arguments→drawing work on the running AutoCAD over COM, or headless ezdxf when AutoCAD is not needed
drives the live AutoCAD process over COM; an open modal dialog in AutoCAD makes calls hangSolidWorks MCP server + automation skill — 66 tools, 66 Python modules
`sw_search_tools`, `sw_describe_tool`, `sw_call_tool`, arguments nested under `params`→sketch / extrude / part / assembly operations, STEP export, four orthographic previews
drives the running SolidWorks instance over COM`deliver` delivery gate
a folder of produced files: `.dxf`, `.dwg`, `.pdf`, `.step`, `.sldprt`/`.sldasm`, `*_review_report.json`→a PASS / warn / FAIL line per check, `delivery.json` with a SHA-256 per file, exit code 0 or 1
starts no CAD application — it only reads what is already on diskContext-token diet
keyword searches issued only when a tool is actually needed→2 entry tools for AutoCAD and 3 for SolidWorks instead of the full 308-tool catalog
every tool call costs one search round-trip first`doctor` / `where` diagnostics
a read-only health report (exit 1 when something is missing) and every path the two servers will use
04Who is it for? When not to use it?
Good for
- Mechanical designers and CAD engineers running dsh (or Codex) on a Windows workstation with AutoCAD and/or SolidWorks installed
- Teams that hand drawings to a reviewer or a shop and need machine-verifiable output
- Drafting leads doing a first-pass review on their own drawings
Not for
- Windows only: the whole point is COM automation of AutoCAD and SolidWorks, so it needs Windows 10/11 with one or both applications installed, plus Python ≥ 3.11.
- The CAD application must already be running as the same user (and integrity level) as the agent. An elevated agent against a normally started CAD session connects to nothing, and it looks like "the tool did nothing".
- Use exactly one install route. The checkout route also writes `~/.dsh/cordis.patch.yml`; with the plugin installed that is a duplicate registration under the same `serverName`, dsh refuses it, and the session fails to start.
- A `deliver` pass means the files hold up as files. It does not check tolerance and fit values (`H7/g6`), material, heat treatment, surface finish, whether a dimension chain closes or whether the part can be machined; the `half` profile only compares values against `lib/standards.json`, and a half pass is not full compliance.
05Compatibility, maintenance and safety notes
- Windows only: the whole point is COM automation of AutoCAD and SolidWorks, so it needs Windows 10/11 with one or both applications installed, plus Python ≥ 3.11.
- The CAD application must already be running as the same user (and integrity level) as the agent. An elevated agent against a normally started CAD session connects to nothing, and it looks like "the tool did nothing".
- Use exactly one install route. The checkout route also writes `~/.dsh/cordis.patch.yml`; with the plugin installed that is a duplicate registration under the same `serverName`, dsh refuses it, and the session fails to start.
- A `deliver` pass means the files hold up as files. It does not check tolerance and fit values (`H7/g6`), material, heat treatment, surface finish, whether a dimension chain closes or whether the part can be machined; the `half` profile only compares values against `lib/standards.json`, and a half pass is not full compliance.
MIT · actively maintained (last push 2026-11-17; no GitHub release yet, the CLI is the delivery surface)
06Frequently asked questions
Do I need both AutoCAD and SolidWorks installed?
No. The plugin probes the COM registry before registering anything and only registers the server it finds — a machine with one CAD registers one server, `SW_CAD_DISABLE=autocad` turns that decision into a setting, and a machine with neither registers nothing and says so instead of offering tools that could only fail.
How do I install it into DeepSeek Harness?
One line: `dsh plugin --profile web add dsh-sw-cad`. package.json declares `dsh.bundle.patch`, so dsh loads `cordis.patch.yml`, inserts one row, resolves its paths and installs the pinned upstream servers on first load — throwing with the failing path if that cannot succeed. `npm install -g dsh-sw-cad` + `dsh-sw-cad install` gives the same result plus the CLI, and a checkout plus `bootstrap.ps1 -Check` is the read-only route. Use one only.
What does the delivery check actually read?
DXF through ezdxf: DIMENSION entities, layer table, `$INSUNITS`, whether a paper-space layout has content, the sheet against ISO 216, whether scale is stated, line weights, the font behind Chinese text, overlapping dimension texts, a title-block hint. PDF through PyMuPDF: page size and whether the text layer is real. STEP: schema resolved to AP203/214/242, entity and CARTESIAN_POINT counts, bounding box. Reports: `evaluation.status == pass`. An empty folder is a failure.
The tools do nothing and report no error — why?
Almost always COM: the CAD application is not running, or it runs as a different user / integrity level than the agent, or a modal dialog is open in AutoCAD. Start AutoCAD / SolidWorks first, as the same user; if AutoCAD tools hang and then mention a dialog, close the licence, save or recovery pane.
What is the `half` profile?
`normal` (default) checks the files; `half` additionally requires the fits (`H7/g6`), material grades (`45`, `40Cr`, `6061`) and roughness written on the drawing to come from `lib/standards.json`, and fails a drawing with no material and no Ra. Set it once per job with `dsh-sw-cad mode half`, or override a single run with `--profile half`. A half pass is not full compliance and the report says so.
07Related DSH workflows
dsh-baton
by jialaoliu
Pass the baton from Claude Code or Codex to a local DeepSeek Harness. An MCP server that hands off tasks and brings the result back.
dsh-crew
by zseven-w
DeepSeek Harness (DSH) plugin: dispatch work to DSH agents from Claude Code / Codex — native subagent progress, in-host worker sessions with per-tier presets, and a multimodal bridge that lends the text-only harness vision and image generation.
dsh-mcp-apps-host
by oriliz
MCP Apps Host plugin for DeepSeek Harness: renders interactive HTML cards from MCP _meta.ui in sandboxed iframes, bridges postMessage to MCP tools/call and resources/read
eac-design-world
by ebony-vinyl
Creates local video and design projects with a timeline, templates, media rendering, preview, and export.
08Data and sources
**1. As a dsh plugin** — the whole install is one line; `package.json` declares `dsh.bundle.patch`, so dsh
loads `cordis.patch.yml`, which inserts one row: this package. On first load the plugin resolves its paths,
`dsh --dump-config` loads both rows from this package.
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-11-20. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.
