Ext Ops Panel
Open dashboard
Comparison

cadbuildr-ai-plugin vs 3D Visualizer

cadbuildr-ai-plugin is a plugin bundle for AI coding tools published by cadbuildr. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 3D Visualizer is an MCP server published by kleinicke. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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

Where each is published
Marketplacecadbuildr-ai-plugin3D Visualizer
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.2
Downloads/month (PyPI): 228
Downloads/week (PyPI): 26
Forks (GitHub): 5
Stars (GitHub): 22
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

cadbuildr-ai-plugin vs 3D Visualizer
Factcadbuildr-ai-plugin3D Visualizer
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)22 (better)
Forks (GitHub) (differs)0 (worse)5 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.cadbuildr.com/mcp)On your machine (3d-visualizer)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)5Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/cadbuildr/cadbuildr-ai-plugingithub.com/kleinicke/ply-visualizer
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-13no 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

cadbuildr-ai-plugin

In its own words, on Claude Code: claude-plugins-community:

AI plugin for working with CADBuildr, a CAD-as-code platform. Skills for project setup, API reference, broker/viewer iteration, and render/export workflows.

3D Visualizer

In its own words, on Official MCP Registry:

Inspect, compare and export point clouds, meshes and calibrated depth data with inline 3D previews.

How to run each

cadbuildr-ai-plugin As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install cadbuildr-ai-plugin@claude-community

3D Visualizer As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio 3d-visualizer -- uvx --with "mcp>=2.2,<3" 3d-visualizer mcp --root "<YOUR_ROOT>"

Requires: --root

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only cadbuildr-ai-plugin 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: cadbuildr-ai-plugin · What it can do: 3D Visualizer · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built