ParCAD vs io.github.mariorojasmz/apolo-cad
ParCAD is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑25.
ParCAD is a plugin bundle for AI coding tools published by Leon Minasian. No marketplace we read lists it any more. io.github.mariorojasmz/apolo-cad is an MCP server published by mariorojasmz. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.mariorojasmz/apolo-cad | |
|---|---|---|
| Community marketplace ierehon1905/parcad | Removed on 2026-10-25 Version: 0.0.13 Forks (GitHub): 1 Stars (GitHub): 10 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 Downloads/month (PyPI): 83 Downloads/week (PyPI): 19 Forks (GitHub): 2 Stars (GitHub): 3 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | ParCADno longer listed · | io.github.mariorojasmz/apolo-cad |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 10 | 3 |
| Forks (GitHub) (differs) | 1 | 2 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (apolo-cad) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence (differs) | AGPL-3.0-or-later | Not stated |
| Repository (differs) | github.com/ierehon1905/parcad | github.com/mariorojasmz/apolo-cad |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of ParCAD
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Brainstorm, design, author, verify, and polish parametric brepjs CAD models
-
Parametric 3D CAD for AI agents: build print-ready parts, check them, export STL, 3MF or STEP.
-
Design 3D-printable parts by chatting: create, edit, render and publish parametric forges.
-
Hardware and EDA toolkit. Drives the KiCad CLI for schematic/PCB export and checks, and OpenSCAD for parametric 3D/2D part design and STL/DXF/PNG output.
-
Build, verify and export 3D CAD parts and assemblies with the ClassCAD engine, running locally.
-
Bitbybit 3D parametric CAD API, version-exact, for coding agents: search, describe, examples, guide
What each says it does
ParCAD
Model 3D-printable parts in a JavaScript DSL on an exact B-rep kernel, over MCP.
io.github.mariorojasmz/apolo-cad
Agent-native parametric 3D CAD: model machines, validate them and emit shop drawings
How to run each
ParCAD
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.mariorojasmz/apolo-cad As a local MCP server: PyPI package
claude mcp add --transport stdio apolo-cad -- uvx apolo-cadCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of ParCAD publish no settings it asks for, so we do not compare settings.
What it can do: ParCAD · What it can do: io.github.mariorojasmz/apolo-cad · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.