Bitbybit CAD MCP vs io.github.printplan3d/ritn3d-mcp
Bitbybit CAD MCP is an MCP server published by bitbybit.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.printplan3d/ritn3d-mcp is an MCP server published by printplan3d. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |   Bitbybit CAD MCP |  io.github.printplan3d/ritn3d-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 1.5.0 Downloads/month (npm): 1 070 Downloads/week (npm): 389 Forks (GitHub): 23 Stars (GitHub): 204 Not marked · First seen |
Listed Version: 0.1.2 Downloads/month (PyPI): 53 Downloads/week (PyPI): 20 Forks (GitHub): 0 Stars (GitHub): 0 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 | Bitbybit CAD MCP | io.github.printplan3d/ritn3d-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 204 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 23 (better) | 0 (worse) |
| Last release (differs) | 2026-10-12 | Not published |
| Where it runs (differs) | Remote server (mcp.bitbybit.dev/mcp) | On your machine (ritn3d-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/bitbybit-dev/bitbybit | github.com/printplan3d/ritn3d-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 34 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
Bitbybit CAD MCP
Bitbybit 3D parametric CAD API, version-exact, for coding agents: search, describe, examples, guide
io.github.printplan3d/ritn3d-mcp
Tools for floor plan validation, GLB checks, and 3D-print unit math — Ritn3D companion.
How to run each
Bitbybit CAD MCP As a remote MCP server
claude mcp add --transport http cad https://mcp.bitbybit.dev/mcpio.github.printplan3d/ritn3d-mcp As a local MCP server: PyPI package
claude mcp add --transport stdio ritn3d-mcp -- uvx ritn3d-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Bitbybit CAD MCP has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of io.github.printplan3d/ritn3d-mcp nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Bitbybit CAD MCP · What it can do: io.github.printplan3d/ritn3d-mcp · Compare two other plugins
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.