MetaForge vs build123d MCP
MetaForge is a plugin bundle for AI coding tools published by MetaForge. Marketplaces we read that list it: 1 (Community GitHub marketplaces). build123d MCP is an MCP server published by pzfreo. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 |  build123d MCP | |
|---|---|---|
| Community marketplace fidelodok/metaforge | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.91 Downloads/month (PyPI): 5 102 Downloads/week (PyPI): 1 587 Forks (GitHub): 16 Stars (GitHub): 118 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 | MetaForge | build123d MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 8 (worse) | 118 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 16 (better) |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (build123d-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 59 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/fidelodok/metaforge | github.com/pzfreo/build123d-mcp |
| Changes in the last 7 days (differs) | 2 | 1 |
| First seen (differs) | 2026-10-18 | 2026-10-11 |
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
MetaForge
Connects to a MetaForge gateway over HTTP. Choose this for a team or hosted gateway, or a local one you already run.
build123d MCP
AI-driven 3D CAD via build123d: execute, render, measure, and export geometry interactively.
How to run each
MetaForge As a Claude Code plugin
/plugin marketplace add fidelodok/metaforge
/plugin install metaforge@metaforgebuild123d 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.
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: MetaForge · What it can do: build123d MCP · 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.