VoltPlan Wiring Diagrams · MCP Server
I refit my boat with Claude as the electrician. Here's the MCP that made it possible.
An MCP server that gives Claude (or any MCP-compatible AI) domain expertise in 12V / 24V / 48V electrical systems — sizing the bank, picking the wire gauge, recommending the fuse, and generating a complete wiring diagram. For boats, campers, vans, and off-grid builds.
[License: MIT]
[npm]
[MCP]
[Hosted]
Drop that into your claude_desktop_config.json, restart Claude, ask: "Plan a 400 Ah lithium house bank for a 30 ft sailboat with 2 days of autonomy." Done.
Why this exists
Built while refitting Largo, a 1996 Maxum, in Roermond. The math kept getting in the way of the work — sizing the bank, then the gauge, then the fuse, then redoing all of it after one load changed. So I gave Claude the math. Now it sizes the bank, picks the gauge, and generates the diagram. I'd rather just do the cabling.
The calculations are the same ones any cruiser or vanlifer ends up doing on graph paper at 11pm. This server makes them a one-sentence prompt.
What it does
Eleven tools, all callable by name from any MCP client:
Demo
Three real prompts, three real outputs.
1. Size a sailboat house bank
"Plan a 400 Ah lithium house bank for a 30 ft sailboat. Loads: 12V fridge 24/7 (60W), LED nav and cabin lights (25W, 4h/day), USB chargers (30W, 2h/day), occasional inverter for a laptop (90W, 3h/day). 2 days of autonomy without solar, LiFePO4 with 80% DoD."
Claude calls calculate_power_budget then calculate_battery_bank:
2. Pick a gauge for an inverter run
"What gauge wire for a 50A inverter run, 3 meters one-way, 12V, marine environment, max 3% drop?"
Claude calls calculate_wire_gauge:
(Ampacity alone would allow 10 mm² / 8 AWG, but voltage drop drives the choice up at this length.)
3. Generate a full schematic
"Generate a wiring diagram for: 2 × 100W solar → MPPT → 200 Ah LiFePO4 → BMV-712 monitor → main 12V bus → fridge, lights, USB."
Claude calls generate_wiring_diagram and shows the schematic as an image: batteries with terminals, MPPT charger, auto-generated shunt, main switch, low-voltage cutoff, and fused load lines in red/black with computed gauges. Below it comes a link that opens the system in the VoltPlan editor with the battery, the solar panel and the first load already placed, to finish, save and turn into a shopping list.
Loads need only power or current, batteries only capacityAh or energyWh; the server derives the rest, and voltages default to the first battery's.
See examples/ for five fully-worked scenarios — sailboat refit, Sprinter van, off-grid cabin, day sailer, live-aboard — each with the prompt, the expected tool calls, and the resulting numbers.
5-minute setup
Claude Desktop (hosted — easiest)
Edit claude_desktop_config.json (Settings → Developer → Edit Config):
Restart Claude. The hammer icon in the chat input means tools are active.
Claude Desktop (local via npx)
Claude Code
Cursor
Edit ~/.cursor/mcp.json (or .cursor/mcp.json per-project):
Cline (VS Code)
Open the Cline panel → MCP Servers → Edit MCP Settings, then:
Self-hosted HTTP server
Docker
Architecture
[Architecture]
Calculations run inside the MCP server and are deterministic. Diagram rendering hits the VoltPlan API and returns a PNG (or SVG) that the AI client shows in the chat, or an interactive viewer in hosts with MCP Apps (see below). find_components and build_bom call VoltPlan's public /api/components/match and /api/diagram/bom endpoints; the shopping list is sized by the same code that renders the diagram. calculate_wire_gauge additionally reads VoltPlan's public catalogue (cached for an hour) to link the recommended cable and fuse to a curated product; without it the links fall back to a store search.
Links and attribution
Buy links go through voltplan.app/api/go with source=mcp, which picks the reader's local Amazon store; VoltPlan earns a commission on purchases (Amazon Associate). Links to voltplan.app pages carry utm_source=mcp.
https://mcp.voltplan.app/mcp-clean serves the same tools without buy links and without pointers to other VoltPlan pages (tool descriptions included). Use it where tool output must not carry promotional content, e.g. Anthropic's connector directory. The diagram's editor link stays, because it opens the generated system for editing. find_components and build_bom return no links at all there: product names, specs, quantities and ratings only. The same holds for the interactive viewer: there it shows a parts list without buy buttons.
Interactive diagram in the chat (MCP Apps)
generate_wiring_diagram declares an MCP Apps view (_meta.ui.resourceUri → ui://wiring-diagram/diagram-viewer-v1.html, spec 2026-01-26). Hosts that support MCP Apps (Claude, ChatGPT, VS Code Copilot, Goose, …) show the diagram as a viewer in the chat instead of a static image:
- zoom (buttons, Ctrl/⌘ + scroll, pinch, double-click), pan by dragging, fit, full screen where the host offers it;
- Open in VoltPlan editor (through the host's
ui/open-link);
- Shopping list (Parts list on
/mcp-clean): calls build_bom with the same system and shows it as a table below the diagram, with buy buttons on /mcp.
The view gets a light SVG (icons loaded from VoltPlan, the only domain in its CSP resourceDomains) and the shopping list through the tool results' _meta, which the model never sees; the model and hosts without MCP Apps keep getting the PNG and the text. Against a VoltPlan without the ?format=json render mode the viewer shows that PNG instead of the SVG.
The view lives in viewer/ and is bundled into dist/viewer.html by npm run build:viewer (part of npm run build, npm run dev and npm test). Try it locally with the basic-host example of ext-apps: SERVERS='["http://localhost:3001/mcp"]' npx tsx serve.ts.
Telemetry
The server sends anonymous usage events to VoltPlan's cookieless analytics (Umami): connection handshakes and tool calls, with the tool name, a few coarse inputs (system voltage, output format, product category) and the client's product name (e.g. claude-ai, from the MCP clientInfo or the HTTP User-Agent). No prompts, no tool arguments beyond those, no IP-derived identifiers. Events record the endpoint as their page (/mcp or /mcp-clean). Set VOLTPLAN_TELEMETRY=off to disable it.
Examples
Worked scenarios in examples/:
Roadmap
- AC-side calculations: shore power inlet, breaker panel sizing, isolation transformer
- More battery chemistries: AGM/Gel sizing curves, lead-carbon
- Multi-bank topologies: starter + house with combiner / DC-DC charger
- Wire run optimization: shared trunks, terminal block placement
Related
About
Built by Stefan Lange-Hegermann (yuzuhub.com). Powered by VoltPlan.
Issues, ideas, and pull requests welcome on GitHub.
License
MIT — see LICENSE.