ohmstead-mcp
Official# Ohmstead MCP server
[Ohmstead](https://ohmstead.io?ref=mcp) is electrical CAD software for wiring schematics: you type the wires
as rows, and it draws the schematic, terminal strips and PDF drawing set. This package lets Claude (and other MCP
clients) do the typing: add parts from the Codex, wire components, run checks and fix fan-outs in your
Ohmstead projects, as you.
You need an Ohmstead account: download the app and sign in with your email. Pro and Student get every tool. Free accounts can read projects, search the Codex and run checks
([plans](https://ohmstead.io/?ref=mcp#pricing)).
## Why it's different
Most schematic MCP servers drive a CAD program: they click, place symbols and draw lines in EPLAN, AutoCAD
Electrical, Altium or KiCad while it runs on your machine. Ohmstead has no drawing to drive. A project is data
(parts, wire rows, strips, cables), so the assistant edits the design itself and Ohmstead draws the result.
- **Official.** Made by Ohmstead and listed in the MCP Registry as `io.ohmstead/mcp`.
- **Wires, not coordinates.** `PSU1:+ → TB1:3` is the whole instruction. Forty I/O points are one call.
- **It checks its own work.** `validate_project` sizes wires and fuses (NEC, NFPA 79, ABYC E-11), finds
fan-outs, wrong clamps and mismatched connectors, and `fix_fanouts` / `optimize_strips` repair them.
- **Real parts.** The Codex is a shared library of parts with their terminals, ratings and connectors.
The assistant searches it before it adds anything.
- **From a PDF to a project.** The assistant reads a vendor or EPLAN wiring list and `import_wiring_list`
builds the project, parts and wires.
- **No CAD seat.** One `npx` command on macOS, Windows or Linux.
## Set up
Install the [Ohmstead app](https://ohmstead.io/?ref=mcp#start) and open it once, then sign in here with
the same email (you'll get a code):
```bash
npx -y ohmstead login --desktop
```
**Claude Code**
```bash
claude mcp add ohmstead -s user -- npx -y ohmstead
```
**Claude Desktop** (`claude_desktop_config.json`)
```json
{
"mcpServers": {
"ohmstead": { "command": "npx", "args": ["-y", "ohmstead"] }
}
}
```
Then ask for something real: *"Make a project for a 3-phase motor starter with an E-stop, wire it, and fix
any fan-outs."* Open the project in Ohmstead (reload if it's already open) to see the drawing.
`npx -y ohmstead whoami` shows who is signed in, `logout` signs out. The session is kept in `~/.ohmstead/`.
Company or on-prem server: `npx -y ohmstead login --server https://… --key <anon key>`.
## What it can do
| Area | Tools |
|---|---|
| Projects | `list_projects`, `get_project`, `create_project`, `update_project`, `import_wiring_list`, `export_project_file`, `import_project_file` |
| Components | `add_components`, `update_components`, `remove_components`, `add_subsystem`, `update_subsystem`, `remove_subsystem` |
| Layout and pages | `layout_view`, `set_block_positions`, `clear_block_positions`, `add_page`, `update_page`, `remove_page` |
| Wires and cables | `add_connections`, `update_connection`, `remove_connections`, `add_cable`, `update_cable`, `remove_cable` |
| Terminal strips | `add_terminal_strip`, `fix_fanouts`, `optimize_strips`, `split_strips`, `set_strip_blocks`, `set_strip_parts` |
| P&ID | `add_pid_items`, `update_pid_items`, `add_process_lines`, `link_instrument`, `remove_pid_items`, `remove_process_lines`, `list_pid_symbols`, `add_pid_sheet`, `update_pid_sheet`, `remove_pid_sheet` |
| Checks | `validate_project`, `allow_multiple_wires` |
| Codex (parts library) | `search_codex`, `save_part`, `add_part_terminals`, `fork_part`, `list_signal_types`, `save_signal_type`, `list_manufacturers` |
Everything runs under your account's permissions, the same as the app. It reads and edits; it never deletes
projects or Codex parts.
## Source
`src/` is the server: `stdio.ts` starts it, `tools.ts` defines every tool, `ohmstead.ts` reads and writes
projects and the Codex through Supabase as the signed-in user, and `auth.ts` / `config.ts` handle sign-in.
The drawing, sizing and checking engine is shared with the Ohmstead app and ships bundled inside the
[`ohmstead`](https://www.npmjs.com/package/ohmstead) npm package (`build.mjs` makes that bundle). The
Dockerfile runs the published package.
Licensed under the [Functional Source License 1.1, MIT future license](LICENSE.md).
Requires Node 20+. Questions: [howdy@ohmstead.io](mailto:howdy@ohmstead.io).
TDQS
Scored across 53 tools
Most tools map cleanly to one resource plus one action, and the descriptions go out of their way to state scope limits (e.g. remove_cable 'never deletes projects or Codex parts'). The risk areas are the strip cluster (add_terminal_strip / fix_fanouts / optimize_strips / split_strips / set_strip_blocks / set_strip_parts) and the frame-placing pair add_page vs add_pid_sheet, which both describe a 1504×800 frame at x,y on different canvases. Careful reading resolves these, but an agent skimming names could misfire.
Strong snake_case verb_noun pattern throughout: get/update/create/list/export/import_project, add/update/remove_components, add/update/remove_pid_items, add/update/remove_pid_sheet. Minor deviations: singular/plural drift (add_connections/remove_connections vs update_connection; pid_items vs pid_sheet), the bare whoami, and the verb-less-ish allow_multiple_wires. Readable and predictable overall.
53 tools is far past a comfortable surface for an agent, even granting that this server spans several genuinely large domains (schematic editing, terminal-strip engineering, P&ID, layout/pages, Codex library). Several near-sibling tools (three page tools, three P&ID sheet tools, six strip tools, three cable/harness tools) could plausibly be consolidated or gated by mode. The count makes tool selection costly rather than impossible.
Coverage is unusually thorough: full CRUD across projects, components, subsystems, wires, cables, strips, P&ID items/lines/sheets, plus layout, validation, sizing explanation, and a parts/signal-type library with fork and search. Notable gaps: there is no delete_project tool at all (remove_cable and remove_connections explicitly disclaim project deletion), and no remove_part or remove_signal_type, so lifecycle teardown of top-level entities is app-only. An agent can work around these but will hit a dead end when asked to delete a project or owned Codex part.