aidc-design-engine vs VMware Private AI (GPU & Model Serving)
aidc-design-engine is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
aidc-design-engine is a plugin bundle for AI coding tools published by AIDC-AI.IO. No marketplace we read lists it any more. VMware Private AI (GPU & Model Serving) is an MCP server published by vmware-skills. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 | ||
|---|---|---|
| Community marketplace aidc2026ai-melon/aidc-design-engine | Removed on 2026-10-16 Version: 0.1.1 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.4.2 Downloads/month (PyPI): 943 Downloads/week (PyPI): 118 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 | aidc-design-engineno longer listed · | VMware Private AI (GPU & Model Serving) |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 1 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-19 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (vmware-privateai) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/aidc2026ai-melon/aidc-design-engine | github.com/vmware-skills/vmware-privateai |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-14 | 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 aidc-design-engine
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
design-engine io.aidc-ai/design-engine
AI data-center design engine: size, validate & lay out Rubin-era data centers. Korea live.
-
LLM serving capacity planner: VRAM, KV cache, GPU topology, latency, and cost.
-
Audit an MCP config, price a model, size a GPU, explain network config drift. Key-free.
-
Read-only GPU advisor: model VRAM needs, fit checks and rental prices, with evidence grades.
-
Search AI infrastructure, inspect facility evidence and explore sourced company relationships.
-
ai-economics pl.piszczek/ai-economics
12 calculators for AI cost, energy and agent verification. Free API, no key.
What each says it does
aidc-design-engine
AI data center design engine — size, validate, and lay out AI/GPU data centers (NVIDIA Hopper / Blackwell / Vera Rubin) with deterministic rack, PUE, MVA, cost, and layout outputs backed by aidc-ai.io.
VMware Private AI (GPU & Model Serving)
VMware Private AI (NVIDIA): GPU inventory, vGPU profiles, utilization, model serving — 18 tools
How to run each
aidc-design-engine
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
VMware Private AI (GPU & Model Serving) As a local MCP server: PyPI package
claude mcp add --transport stdio vmware-privateai -- uvx vmware-privateai mcp
Commands 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: aidc-design-engine · What it can do: VMware Private AI (GPU & Model Serving) · 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.