Use MiniRackBuilder from your AI assistant
AI assistant buttons are hidden in the planner on this device.
MiniRackBuilder has a free MCP server. Connect it once and your AI assistant can search real 6", 7" and 10" mini racks and parts, check that a build fits, save it, and change it while you watch in the browser. No account or API key needed.
Server address
Paste this wherever your app asks for a remote MCP server or connector URL. It uses Streamable HTTP and needs no sign-in.
https://minirackbuilder.com/mcpConnect your app
Claude (claude.ai and Claude Desktop)
- Open Customize > Connectors (on Team or Enterprise plans an Owner adds it under Organization settings > Connectors).
- Choose Add, then Add custom connector.
- Name it MiniRackBuilder, paste the server URL above and click Continue. Keep No sign-in, then click Add.
- In a chat, turn it on under + > Connectors. The connector works the same in the desktop app.
Claude Code
Add --scope user to use it in every project. Run /mcp inside Claude Code to check that it connected.
claude mcp add --transport http minirackbuilder https://minirackbuilder.com/mcpChatGPT
- On chatgpt.com, open Plugins, choose + and then Add custom MCP server. On some plans this is under Settings > Apps after turning on Developer mode.
- Enter the name MiniRackBuilder and the server URL above, and choose No authentication.
- Confirm the warning, create it, and turn it on in the chat where you want to use it.
Custom MCP servers are only offered on some ChatGPT plans, and OpenAI renames these menus from time to time.
Cursor
{
"mcpServers": {
"minirackbuilder": {
"url": "https://minirackbuilder.com/mcp"
}
}
}VS Code (GitHub Copilot agent mode)
Or run MCP: Add Server from the Command Palette, choose HTTP and paste the server URL. Note the key is servers, not mcpServers.
{
"servers": {
"minirackbuilder": {
"type": "http",
"url": "https://minirackbuilder.com/mcp"
}
}
}opencode
Run opencode mcp list to check that it connected. To add it by hand instead, put {"type": "remote", "url": "https://minirackbuilder.com/mcp", "oauth": false} under mcp.servers.minirackbuilder in your opencode config. Older opencode versions put the name directly under mcp.
opencode mcp add minirackbuilder --url https://minirackbuilder.com/mcpOther apps
Any app that supports remote MCP servers over Streamable HTTP can use the server URL above. Apps that only run local servers cannot connect to it.
What to expect
- Builds are private by default. A saved build is Unlisted (link only): only people with the link can see it. The assistant makes it Public in catalog only when you ask it to.
- The edit key is secret. When the assistant saves a build it gets an edit key. The link it gives you to watch live ends in
#edit=…: that part is the key. Anyone who has it can change or delete the build, so do not post that link. - Watch it live. Open the live link and the rack updates in your browser as the assistant works. If you change something yourself, live updates pause and you choose whose version to keep.
- Starting from scratch. In the planner, click Copy a starter prompt under the buttons and paste the prompt into your assistant. Nothing needs to be saved first: the assistant saves a new build and gives you the live link.
- Not interested? Click Hide next to the starter prompt and the planner never shows AI assistant buttons on this device. You can turn them back on from this page.
- Editing an existing build. In the Save dialog, on your build's page or in My Saved Builds, use Copy MCP Prompt and paste it into your assistant. For someone else's build, the same button gives a prompt that saves a private copy for you.
- Cables use the planner's own ports. The assistant checks the build first and copies port names from the list it gets back, so every cable shows up in the planner. A cable to a port that does not exist is reported and not saved.
- Deleting only happens when you ask for it, and cannot be undone.
Example prompt
Using the MiniRackBuilder MCP server, plan an 8U 10-inch homelab rack with a 2.5GbE PoE switch, a mini PC running Proxmox, a patch panel and a PDU. Check that everything fits the rack depth and the power budget, save it, and give me the link.Tools the assistant can use
| Tool | What it does | Main inputs |
|---|---|---|
search_racks | Find rack enclosures by height, width (6, 7, 10 or 19 inch), depth or keyword, with current prices. | query, format, min_u, max_u, min_depth_mm, max_depth_mm, region, limit |
search_parts | Find switches, mini PCs, PDUs, patch panels, shelves, PCIe cards and accessories that fit. | query, category, format, max_u, max_depth_mm, has_poe, region, limit |
get_part_details | Full specs and price for up to 10 parts: size, ports, power, drive bays, mounting options. | slugs or slug, region |
search_catalog_extras | List 3D-printable mounts, starter builds and community parts. | kind, query, limit |
validate_build | Check a build without saving it: overlaps, rack width and depth, shelves, power, cables. | rack, slots, rear_slots, cables, extras, … |
create_build | Save a new build. It is Unlisted (link only) unless you ask the assistant to make it Public in catalog. | rack, slots, title, visibility, … |
update_build | Change a saved build with its edit key. Only the parts it sends change, and open browser tabs in live mode update right away. | build_id, edit_token, base_rev, visibility, … |
get_build | Read a saved build and its current revision. Never shows the edit key. | build_id |
delete_build | Delete a build for good, only when you ask for it. | build_id, edit_token |
render_rack_preview | Draw the rack as a picture so the assistant can check its own work. | build_id or build, view, theme |
Rack pictures for READMEs and docs
Every saved build has a picture at https://minirackbuilder.com/b/<id>/rack.png that follows the latest version of the build. Options:
?theme=darkor?theme=light(dark is the default).?view=front,?view=rearor?view=both. By default you get both sides when the rear is used, except on racks taller than 24U, which show the front only so the picture stays readable. Rear parts are always listed beside the rack.
Replace <id> with your build ID. Your build page has buttons that copy this with the ID filled in.
<a href="https://minirackbuilder.com/b/<id>">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://minirackbuilder.com/b/<id>/rack.png?theme=dark">
<img alt="My rack" src="https://minirackbuilder.com/b/<id>/rack.png?theme=light" width="680">
</picture>
</a>Troubleshooting
- The assistant does not see the tools. Check that the connector is turned on for this chat (Claude: + > Connectors), or restart the app after editing a config file. In Claude Code,
/mcpshows the connection status. - "Connection failed" when adding it. Use the full URL ending in
/mcp, with https, and choose no sign-in or no authentication. - The assistant says the edit key is wrong. Copy a fresh prompt with Copy MCP Prompt from your build's page. The key only works on the build it belongs to.
- The assistant says the build changed. Someone (maybe you, in the browser) saved a newer version since the assistant last read it. Ask it to read the build again with get_build and redo its change.
- The live page says "Connection lost". It keeps retrying by itself. If it says the build was deleted, live updates stop for good.
- A cable shows "Removed part". One of its ends points at a port that no longer exists, often after a part was swapped. Ask the assistant to run get_build and fix or remove the cables it flags.
- The rack picture looks out of date. Pictures can be cached for a few minutes by GitHub and browsers.
For developers: /.well-known/mcp.json · /llms.txt