RackArchitect MCP
Related Servers
Alternatives to RackArchitect MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceEnables AI agents to generate dimensionally accurate mechanical parts (gears, enclosures, brackets, assemblies) in headless Blender from plain-English specs or JSON parameters, then verify them against manifold, bounding-box and print-production gates and export glTF/STL assets. It also scaffolds interactive Three.js CAD viewer pages with orbit controls, wireframe toggles and exploded-view scrubbing.4117-
- AlicenseAqualityCmaintenanceDeterministic AI data-center design tools for sizing, validation, and conceptual rack/site layouts. Supports NVIDIA Hopper, Blackwell, and Rubin profiles. Calculations require a registered AIDC API key; results preserve warnings, RFIs, and pending validations.33MIT
- AlicenseAqualityAmaintenanceFloor plans as code. Your AI writes ArchLang; the compiler draws a precise, dimensioned plan and tells it what's wrong.112,954 npm81MIT
- AlicenseAqualityBmaintenanceEnables generating parametric 3D-printable parts from OpenSCAD/CadQuery models, exporting STL/3MF files, running DFM checks, and retrieving Bambu X1 Carbon starting profile notes.8MIT
- AlicenseBqualityBmaintenanceEnables AI agents to plan, generate, inspect, validate, repair, preview and hand off 3D models across five interchangeable geometry engines (procedural, OpenSCAD, Blender, CadQuery and hosted text-to-3D). Profile-based validation for print, CAD, game and web purposes keeps outputs correct, while CPU previews and single-file Three.js viewers make results visible and shareable.213MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants and MCP-compatible clients to create, iterate on, preview, validate, and export 3D models from natural-language OpenSCAD code with zero setup, bundled BOSL2, multi-view renders, turntable previews, and a live browser viewer.GPL 2.0
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose, and descriptions explicitly cross-reference alternatives such as mount vs. modify, connect vs. disconnect, and validate vs. export. Overlapping-sounding operations like removing a device versus disconnecting cables are sharply separated.
All tool names use snake_case and follow a predictable verb_noun or verb_object pattern. The only slight outlier, undo_redo, is a conventional paired-action name and does not disrupt the pattern.
Twelve tools is well-scoped for a rack design server covering initialization, catalog management, mounting, cabling, validation, export, and undo. Each tool appears to earn its place without excessive surface area.
The surface covers the core rack lifecycle: init, catalog discovery and registration, mount/modify, cable operations, external endpoints, validation, export, and undo. Minor gaps exist, such as no dedicated read-only list/get mounted devices tool and no explicit custom-blueprint deletion, but agents can work around these via validate_rack and catalog behavior.