Pascal 3D Editor vs build123d MCP
Pascal 3D Editor is an MCP server published by pascal.app. Marketplaces we read that list it: 1 (Official MCP Registry). build123d MCP is an MCP server published by pzfreo. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-27. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Pascal 3D Editor |  build123d MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.6 Forks (GitHub): 3 126 Stars (GitHub): 25 119 Not marked · First seen |
Listed Version: 0.3.91 Downloads/month (PyPI): 5 102 Downloads/week (PyPI): 1 819 Forks (GitHub): 18 Stars (GitHub): 131 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.3.91 Downloads/month (PyPI): 5 102 Downloads/week (PyPI): 1 819 Forks (GitHub): 18 Stars (GitHub): 131 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 | Pascal 3D Editor | build123d MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 25 119 (better) | 131 (worse) |
| Forks (GitHub) (differs) | 3 126 (better) | 18 (worse) |
| Last release (differs) | 2026-10-23 (better) | 2026-10-16 (worse) |
| Where it runs (differs) | Remote server (editor.pascal.app/api/mcp) | On your machine (build123d-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/pascalorg/editor | github.com/pzfreo/build123d-mcp |
| Changes in the last 7 days (differs) | 3 | 0 |
| First seen (differs) | 2026-10-23 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 42 h ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Pascal 3D Editor
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
build123d MCP
AI-driven 3D CAD via build123d: execute, render, measure, and export geometry interactively.
How to run each
Pascal 3D Editor As a remote MCP server
claude mcp add --transport http editor https://editor.pascal.app/api/mcpbuild123d MCP As a local MCP server: PyPI package
claude mcp add --transport stdio build123d-mcp -- uvx build123d-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Pascal 3D Editor has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Pascal 3D Editor · What it can do: build123d MCP · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.