Skip to content
Back to search

partcad

MarketplaceWorks with Claude CodeGitHub

PartCAD skills for AI coding agents

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/partcad/partcad with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/partcad/partcad'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/partcad--partcad/badge.svg)](/listings/partcad--partcad)

HTML

<a href="/listings/partcad--partcad"><img src="/api/listings/partcad--partcad/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

Note, it's not required but highly recommended that you have [conda] installed. If you experience any difficulty installing or using any PartCAD tool, then make sure to install [conda].

That applies to the Python packages below. The standalone command line tools, the snap and the PartCAD IDE carry a conda of their own and need none installed — they use yours when you have one.

Plugin for Claude Code

Already using [Claude Code](https://claude.com/claude-code)? This is the shortest way in, and it installs everything else for you. The `pc` plugin adds skills that generate parts, assemblies and 2D sketches, describe and search what a package already has, and set up the tools themselves:

/plugin marketplace add partcad/partcad@plugin-dist
/plugin install pc@partcad

Then `/pc:setup` puts the command line tools on the machine -- and, when it is run from a Visual Studio Code or VSCodium terminal, the extension below into that editor -- `/pc:init` starts a package, and `/pc:gen a mounting bracket with four M4 holes` writes the CAD script, renders four views of what came out and checks them against what was asked. The skills drive the same `pc` commands documented below, so nothing they produce is locked to the agent that produced it.

This repository *is* the marketplace -- there is no hosted catalog to search. The `plugin-dist` branch above carries the latest release, symlink-free so that it installs the same way on Windows. Two alternatives: `/plugin marketplace add partcad/partcad` installs straight from the source tree (git has to be able to create symlinks, which on Windows means `git config core.symlinks true`), and every [release](https://github.com/partcad/partcad/releases) carries a `pc-<version>.zip` that `claude --plugin-url <url>` loads for a single session, to try one version without installing it.

The skills are plain [Agent Skills](https://code.claude.com/docs/en/skills), so any `SKILL.md`-aware agent can read them out of [`ai-agents/`](./ai-agents/README.md) without the plugin. They also ship inside the `partcad` wheel, and `pc init` installs them into the repository it creates a package in: the plugin for Claude Code, and `pc-`-prefixed skills for Cursor. Pass `--no-skills` to skip it, or `--skills-only` to install them into a repository that has a package already.

MCP server

`pc mcp` serves the [Model Context Protocol](https://modelcontextprotocol.io) on stdio, so that any MCP client -- Claude Code, Claude Desktop, Cursor, VS Code -- can drive PartCAD: list what a package holds, read an object's declaration, look at it (renders come back as images), test it and export it, and reach every other daemon method through one `execute` tool. It is a client of the workspace's daemon like every other `pc` command, and it only touches files inside the workspace unless started with `--allow-path`.

The `pc` plugin above brings it along, the VS Code extension registers it with the editor, and `pc init` writes it into the `.mcp.json` and `.cursor/mcp.json` of the repository it sets up. Anywhere else:

claude mcp add partcad -- pc mcp     # with PartCAD installed
claude mcp add partcad -- uvx partcad mcp

It is also listed in the [MCP Registry](https://registry.modelcontextprotocol.io) as `io.github.partcad/partcad`. See [the documentation](https://partcad.readthedocs.io/en/latest/mcp.html) for the tools and other clients.

PartCAD IDE

The whole thing in one application: the editor, the PartCAD extension, and the command line tools. No Python, no extensions to pick, no environment to set up. It opens in the PartCAD workbench, and the first time it starts it creates a package for you and opens that -- so there is something to render before there is anything to read.

curl -fsSL https://raw.githubusercontent.com/partcad/partcad/main/install.sh | sh -s -- --ide

On Windows, download and run `partcad-ide-<version>-windows-x86_64-setup.exe` from the

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 16 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
  3. "name": "partcad",
  4. "description": "PartCAD skills for AI coding agents",
  5. "owner": {
  6. "name": "Roman Kuzmenko",
  7. "email": "rkuz@partcad.org"
  8. },
  9. "plugins": [
  10. {
  11. "name": "pc",
  12. "description": "Mechanical and robotics engineering with PartCAD",
  13. "source": "./ai-agents/claude"
  14. }
  15. ]
  16. }
README.md · README · 102 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # PartCAD <!-- omit in toc -->
  2. [![CI on Linux, macOS and Windows](https://github.com/partcad/partcad/actions/workflows/test.yml/badge.svg?event=schedule)](https://github.com/partcad/partcad/actions/workflows/test.yml?query=event%3Aschedule)
  3. [![PyPI](https://img.shields.io/pypi/v/partcad)](https://pypi.org/project/partcad/)
  4. [![Documentation Status](https://readthedocs.org/projects/partcad/badge/?version=latest)](https://partcad.readthedocs.io/en/latest/?badge=latest)
  5. [![Discord](https://img.shields.io/discord/1308854595987968051?logo=discord&logoColor=white&label=Discord&labelColor=353c43&color=31c151)](https://discord.gg/h5qhbHtygj)
  6. [![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](https://github.com/partcad/partcad/blob/main/LICENSE.txt)
  7. **[PartCAD] is the programming language for manufacturable things.**
  8. A package is a Git repository with a `partcad.yaml` that declares parts (CAD scripts or files), assemblies,
  9. materials and requirements. PartCAD renders, tests, simulates, analyses and documents them, and produces the
  10. bill of materials, the sourcing and the assembly instructions from that same source. Everything is text, so it
  11. is versioned, reviewed and generated like software, by people and by AI agents.
  12. [Documentation](https://partcad.readthedocs.io/) · [Website](https://partcad.org/) ·
  13. [Demos](https://youtube.com/@PartCAD) · [Discord](https://discord.gg/h5qhbHtygj)
  14. [![PartCAD in Visual Studio Code](https://github.com/partcad/partcad/blob/main/docs/source/images/vscode1.png?raw=true)](https://marketplace.visualstudio.com/items?itemName=PartCAD.partcad-official)
  15. ## Install
  16. Pick one. Every option ends up with the same `pc` command line tool and the same packages.
  17. | You have | Install |
  18. | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
  19. | Nothing yet | The **PartCAD IDE**: `curl -fsSL https://raw.githubusercontent.com/partcad/partcad/main/install.sh \| sh -s -- --ide`, or the Windows and macOS installers on the [releases page](https://github.com/partcad/partcad/releases) |
  20. | Python | `pip install -U partcad` |
  21. | Visual Studio Code | `code --install-extension PartCAD.partcad-official` ([marketplace](https://marketplace.visualstudio.com/items?itemName=PartCAD.partcad-official)) |
  22. | Claude Code | `/plugin marketplace add partcad/partcad@plugin-dist`, then `/plugin install pc@partcad`, then `/pc:setup` |
  23. The standalone command line tools without Python, the snap, the FreeCAD add-on, the MCP server for other AI
  24. agents, and the per-OS notes are all in
  25. [Installation](https://partcad.readthedocs.io/en/latest/installation.html).
  26. ## Try it
  27. ```shell
  28. pc init # a package in the current directory, with agent skills for Claude Code and Cursor
  29. pc ide view my_part # show it in the Digital Thread of the IDE or the extension
  30. pc render my_part # SVG, PNG, DXF... from any angle
  31. pc qual test # qualify: basic, topology (overlaps, untoleranced faces), simulation, plugins
  32. pc instructions my_assembly # the assembly instruction book, PDF or HTML, with the bill of materials
  33. ```
  34. Or, in Claude Code, `/pc:gen a mounting bracket with four M4 holes`: the agent writes the CAD script, renders
  35. it and checks the result against what was asked.
  36. The [tutorial](https://partcad.readthedocs.io/en/latest/tutorial.html) walks through a first package, and
  37. [`examples/`](https://github.com/partcad/partcad/tree/main/examples) has one directory per feature.
  38. ## What it does
  39. - **Parts** from [CadQuery], [build123d], [OpenSCAD], [Chili3D], [SDF], STEP, BREP, IGES, STL, 3MF, OBJ, glTF,
  40. FreeCAD, Autodesk Fusion, SolidWorks, Autodesk Inventor, CATIA V5, ACIS and Creo View files, OpenUSD stages,
  41. [KiCad EDA] PCBs, and any format a plugin package adds ([SolidCraft], Rhino).
  42. - **Assemblies and scenes** in Assembly YAML, URDF, or a STEP, Autodesk Fusion or Creo View file, with interfaces
  43. and mating as objects.
  44. - **Outputs**: STEP, BREP, STL, 3MF, OBJ, IGES, glTF, URDF, Gazebo and MuJoCo worlds, 2D projections,
  45. dimensioned drawings, Markdown documentation and PDF or HTML instruction books.
  46. - **Engineering**: FEA, modal, thermal and CFD analysis (`pc cae`), simulation in MuJoCo or Gazebo
  47. (`pc qual test --simulation`), 2.5D toolpaths (`pc cam`), and materials and manufacturing methods carried into the bill of
  48. materials.
  49. - **Supply chain**: a Build vs Buy decision per line item, stock-based procurement for made parts, and
  50. automated purchasing from the command line.
  51. - **AI agents**: Agent Skills for Claude Code and Cursor, an MCP server (`pc mcp`), and plain-text
  52. `--no-ansi` output on every command.
  53. - **Caching** in memory, on disk, in memcached and in S3, so a team or a CI fleet renders each model once.
  54. The full list of what is supported, and what is still in progress, is in
  55. [Supported formats and features](https://partcad.readthedocs.io/en/latest/supported.html).
  56. ## Why
  57. PartCAD is not a drawing tool. It is the layer under the drawing tools: the specification of a manufacturable
  58. product, kept in a form that a human, a CI job and an AI model can all read, change and verify. Keeping that
  59. specification on-prem, in Git, and portable between CAD tools and manufacturers is the point. See
  60. [Introduction](https://partcad.readthedocs.io/en/latest/intro.html) and
  61. [Use cases](https://partcad.readthedocs.io/en/latest/use_cases.html).
  62. ## Community
  63. Questions and feedback go to [Discord](https://discord.gg/h5qhbHtygj); bugs and ideas to
  64. [GitHub issues](https://github.com/partcad/partcad/issues). Follow [LinkedIn], [YouTube] and [Twitter/X] for
  65. releases. To contribute, start with
  66. [Contributing](https://partcad.readthedocs.io/en/latest/contributing.html).
  67. Licensed under [Apache 2.0](https://github.com/partcad/partcad/blob/main/LICENSE.txt).
  68. <!-- mcp-name: io.github.partcad/partcad -->
  69. [PartCAD]: https://partcad.org/
  70. [LinkedIn]: https://linkedin.com/company/partcad
  71. [YouTube]: https://youtube.com/@PartCAD
  72. [Twitter/X]: https://x.com/PartCAD
  73. [CadQuery]: https://github.com/CadQuery/cadquery
  74. [build123d]: https://github.com/gumyr/build123d
  75. [Chili3D]: https://github.com/xiangechen/chili3d
  76. [OpenSCAD]: https://openscad.org/
  77. [SDF]: https://github.com/fogleman/sdf
  78. [KiCad EDA]: https://www.kicad.org/
  79. [SolidCraft]: https://github.com/bherbruck/solidcraft

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.