io.github.itAlex240/rack-architect-mcp

None of its 12 tools are described as changing anything. For 12 the reading was uncertain, so no mark is shown.

• search_catalogon 109 other servers

  “Search and filter the local hardware catalog to discover compatible rackmount devices, modular carriers, and sub-modules before mounting.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  7 inputs

  • querystring“Optional case-insensitive substring filter matching slug, manufacturer, or model name (omit to match all).”
  • form_factorstring“Primary rack width or mounting form-factor filter (shorthands "10inch", "19inch", and "6inch" match both direct rackmount equipment and modular carriers of tha…”
  • mount_typestring“Optional alias for form_factor to filter by physical mounting style ("rackmount-10", "rackmount-19", "rackmount-6", "sub-module", or "shelf-standing"); combine…”
  • categorystring“Functional hardware category filter (e.g., "switch", "router", "ups", "pdu", "patch-panel", "modular-carrier", "mini-pc", "sbc").”
  • max_depth_mmnumber“Maximum allowed chassis depth in millimeters (inclusive upper bound).”
  • min_poe_budget_wattsnumber“Minimum required PSE PoE output power budget in watts (inclusive lower bound).”
  • accepted_slot_typestring“Sub-module slot compatibility token matching either a sub-module slot_compatibility or a carrier slot accepted_slot_type (e.g., "mini-pc-1liter", "sbc-rpi5", "…”
• get_device_blueprint

  “Retrieve the complete hardware specification, millimeter port coordinates, electrical and PoE ratings, and carrier slot geometry for a single catalog blueprint.”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  1 input, 1 required

  • slugstringrequired“Exact lowercase kebab-case hardware catalog blueprint slug to retrieve (discoverable via search_catalog).”
• define_custom_blueprint

  “Validate and register a custom hardware blueprint into the active catalog so unlisted equipment can be mounted.”

  Publisher declares: read-only no · destructive no · idempotent yes · open-world no

  1 input, 1 required

  • blueprintobjectrequired“Complete custom hardware blueprint specification; ports may be defined via explicit ports[], repeating port_groups[] macros, or both.”
• init_rack

  “Initialize a new rack project and destructively reset the active rack.yaml state to an empty enclosure with the specified width standard, U height, and rail depth.”

  Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

  7 inputs, 3 required

  • project_namestring“Human-readable project name stored in rack.yaml.”
  • standardstringrequired“Mechanical rack width standard ("19inch" = 482.6mm, "10inch" = 254.0mm, "6inch" = 152.4mm).”
  • u_heightintegerrequired“Total usable vertical rack height in Rack Units (1U = 44.45mm, 1..60U).”
  • rail_depth_mmnumberrequired“Front-to-rear mounting rail depth in millimeters along the Z-axis (max 2000mm).”
  • enclosure_typestring“Enclosure door style ("open-frame", "closed-glass-front", or "closed-vented-front").”
  • front_door_clearance_mmnumber“Available clearance in millimeters between front mounting rails (Z=0) and a closed front door.”
  • rear_clearance_mmnumber“Available clearance in millimeters behind the rear mounting rails (Z=rail_depth_mm) for power plugs and bending radii.”
• mount_equipment

  “Mount a new hardware device instance onto a rack unit or into a modular carrier bay in the active rack.yaml project and run 5-stage validation.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world no

  7 inputs, 2 required

  • instance_idstringrequired“Unique project-wide instance identifier for this mounted device (e.g., "ups-u1", "sw-core-01").”
  • blueprint_slugstringrequired“Catalog or custom hardware blueprint slug to instantiate.”
  • hostnamestring“Optional logical hostname or display label shown in elevations and schematics.”
  • u_positioninteger“1-indexed lowest Rack Unit (U) when mounting directly onto the rack rails (mutually exclusive with parent_carrier_id/slot_id).”
  • facestring“Target rack mounting face ("front" or "rear") for direct rackmount equipment.”
  • parent_carrier_idstring“Mounted parent modular-carrier instance_id when mounting a sub-module (requires slot_id; mutually exclusive with u_position).”
  • slot_idstring“Target bay slot_id inside parent_carrier_id when mounting a sub-module (e.g., "left-bay", "keystone-1").”
• modify_equipment

  “Move, rename, or destructively remove an existing mounted device or child sub-module in the active rack, recalculate 3D cable splines, and re-run 5-stage validation.”

  Publisher declares: read-only no · destructive yes · idempotent no · open-world no

  11 inputs, 2 required

  • instance_idstringrequired“Existing mounted device or child sub-module instance_id to modify.”
  • actionstringrequired“Modification operation: "move" relocates a device, "rename" updates its hostname, and "remove" deletes the device instance.”
  • u_positioninteger“New 1-indexed U position when action is "move" on a direct rackmount device (takes precedence over new_u_position).”
  • new_u_positioninteger“Optional alias for u_position when action is "move".”
  • facestring“New mounting face ("front" or "rear") when action is "move" on a rackmount device (takes precedence over new_face).”
  • new_facestring“Optional alias for face when action is "move".”
  • parent_carrier_idstring“Target parent carrier instance_id when action is "move" on a child sub-module.”
  • slot_idstring“Target slot_id inside parent_carrier_id when action is "move" on a child sub-module.”
  • hostnamestring“New logical hostname when action is "rename" (takes precedence over new_hostname).”
  • new_hostnamestring“Optional alias for hostname when action is "rename".”
  • remove_connected_cablesboolean“When action is "remove", whether to automatically disconnect all cables and external endpoints attached to the removed device (default: true).”
• connect_cables

  “Connect or update a batch of up to 128 power and network cables between mounted device ports in the active rack, computing 3D Catmull-Rom splines, commercial length bins, and PoE or power budgets.”

  Publisher declares: read-only no · destructive no · idempotent yes · open-world no

  1 input, 1 required

  • cablesarrayrequired“Batch of one or more cable connections to upsert by cable_id, route in 3D, and validate (max 128 per call).”
• disconnect_cables

  “Remove specific cables by identifier or strip all cables attached to a mounted device or modular carrier from the active rack, then re-evaluate PoE budgets and plug clearances.”

  Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

  2 inputs

  • cable_idsarray“Specific cable_id values to disconnect (can be combined with instance_id; at least one of cable_ids or instance_id must be provided).”
  • instance_idstring“Mounted device or modular-carrier instance_id whose attached cables (including child sub-module cables) should all be disconnected.”
• plan_external_endpoints

  “Terminate external building or room cable drops onto the rear RJ45 ports of a mounted patch panel without consuming rack U slots, and optionally auto-create labeled Cat6A front patch cables to a moun…”

  Publisher declares: read-only no · destructive yes · idempotent no · open-world no

  8 inputs, 1 required

  • patch_panel_instance_idstringrequired“Mounted patch panel instance_id whose rear ports receive the incoming building cable drops.”
  • start_port_numberinteger“1-indexed starting port number on the patch panel (defaults to next free rear port or 1).”
  • entry_positionstring“Rear building cable conduit entry point into the rack frame.”
  • groupsarray“Batch groups of external drops (e.g., 10x PoE cameras, 5x Wi-Fi APs, 5x room LAN outlets).”
  • endpointsarray“Individual external building/room drops to terminate on the rear of the patch panel.”
  • auto_connect_switch_instance_idstring“Optional switch instance_id to automatically patch from the front of the patch panel using labeled Cat6A cables.”
  • auto_connect_switch_start_portinteger“1-indexed starting Ethernet port number on auto_connect_switch_instance_id (e.g., 1 for eth1).”
  • clear_existingboolean“If true, destructively clears existing external_endpoints (and their front patch cables) on patch_panel_instance_id before planning.”
• validate_rack

  “Inspect the active rack.yaml state and run all 5 deterministic validation stages covering mechanical bounds, 3D depth and plug clearances, PoE and power budgets, cable compatibility, and thermal limi…”

  Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

  Takes no inputs.

• export_deliverables

  “Generate 2D elevation and wiring SVGs, a Markdown BOM, a binary 3D GLB scene, and parametric OpenSCAD or watertight STL 3D-print models for the active rack project.”

  Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

  2 inputs

  • formatsarray“Deliverable formats to generate and write to disk (defaults to all 6 formats; carrier-scad and carrier-stl emit files when modular carriers are mounted).”
  • output_dirstring“Optional target filesystem directory for generated files in local stdio mode (defaults to the directory of the active rack.yaml file; ignored on hosted remote …”
• undo_redo

  “Traverse the per-project in-memory history ring buffer of up to 50 snapshots to revert the latest rack mutation or reapply a reverted mutation, updating rack.yaml atomically.”

  Publisher declares: read-only no · destructive no · idempotent no · open-world no

  1 input, 1 required

  • actionstringrequired“History traversal direction: "undo" reverts the most recent state mutation, "redo" reapplies a reverted mutation.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-03.

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.