ohmstead-mcp
OfficialOhmstead MCP server
Ohmstead 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).
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:3is the whole instruction. Forty I/O points are one call.It checks its own work.
validate_projectsizes wires and fuses (NEC, NFPA 79, ABYC E-11), finds fan-outs, wrong clamps and mismatched connectors, andfix_fanouts/optimize_stripsrepair 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_listbuilds the project, parts and wires.No CAD seat. One
npxcommand on macOS, Windows or Linux.
Related MCP server: KiCAD MCP Server
Set up
Install the Ohmstead app and open it once, then sign in here with the same email (you'll get a code):
npx -y ohmstead login --desktopClaude Code
claude mcp add ohmstead -s user -- npx -y ohmsteadClaude Desktop (claude_desktop_config.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 |
|
Components |
|
Layout and pages |
|
Wires and cables |
|
Terminal strips |
|
P&ID |
|
Checks |
|
Codex (parts library) |
|
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 npm package (build.mjs makes that bundle). The
Dockerfile runs the published package.
Licensed under the Functional Source License 1.1, MIT future license.
Requires Node 20+. Questions: howdy@ohmstead.io.
Available Tools
53 toolsadd_cableAdd cableA
Add a multi-conductor cable between two connectors, e.g. from "B1:X1" to "IO1:X2". Pins are mapped 1:1 (same pin names, else pin order) unless conductors are given. Tag defaults to the next free W1, W2…
Inputs: to (required), from (required), project_id (required), tag, +4 more.
add_componentsAdd componentsA
Place Codex parts in a project under unique tags (e.g. PLC_MAIN, PSU1, K1). The part must already exist in the Codex (search_codex / save_part). subsystem = name or id of an existing subsystem.
Inputs: components (required), project_id (required).
add_connectionsAdd wiresA
Append wires (grid rows) between component terminals. Terminals must exist on the Codex part; terminal strips accept new terminal labels. Returns the issues after the change.
Inputs: wires (required), project_id (required).
add_pageAdd print pageA
Place a print page: a fixed 1504 × 800 frame in one view with its top-left at x, y (absolute view coordinates, as layout_view's ax, ay and frames). Blocks whose centre is inside print on it; the rest go on automatic pages after the placed ones. Pages print in the order they were added within each view.
Inputs: x (required), y (required), name (required), project_id (required), +1 more.
add_part_terminalsAdd terminals to a Codex partA
Add terminals to a Codex part. Terminals can carry load_a / rated_a current data (datasheet values, not guesses); the part's other data stays as it is. Your own parts, and team parts in a team where you're an editor or up, are changed in place; anything else is forked into your Codex first (into the team's Codex when project_id is a team project). Pass project_id to relink that project's components to the fork.
Inputs: part_id (required), terminals (required), project_id.
add_pid_itemsAdd P&ID itemsA
Add symbols to the project's P&ID (list_pid_symbols has the keys). With no tag an item gets the next free one (I-1, V-1, P-1, TK-1, E-1; actuators get none). With no position the auto-layout places it. size is for equipment only and snaps to the symbol's 10-unit steps. With component, the item links to that wiring component and the project's tag rule decides what it prints, so the result shows the printed tag.
Inputs: items (required), project_id (required).
add_pid_sheetAdd P&ID sheetA
Add a named print sheet to the P&ID: a frame of 1504 × 800 units with its top-left at x,y. An item prints on the sheet holding its centre, sheets print in the order listed, and items outside every sheet tile onto automatic sheets after them. The result lists what each sheet holds.
Inputs: x (required), y (required), name (required), project_id (required).
add_process_linesAdd process linesA
Draw lines between P&ID items. from and to are "TAG:PORT" or "TAG" (tag or item id; list_pid_symbols has each symbol's ports, and a bare side like 90 on a side with several ports takes the one closest to the other end, so the line runs straight when a port lines up; with no positions, the one closest to the side's centre). kind defaults to process. Signal lines come from the wiring, so draw one only for something not wired yet. A line from an item to itself or an exact duplicate is skipped.
Inputs: lines (required), project_id (required).
add_subsystemAdd subsystemB
Create a subsystem (group) to organize components, optionally nested under a parent subsystem, with its own signal flow.
Inputs: name (required), project_id (required), flow, parent.
add_terminal_stripAdd terminal stripA
Add a terminal strip (auto-tagged TB1, TB2…). Usually fix_fanouts creates strips for you; use this for planned strips. Its terminals use block if given, else the project default block, else a generic block (terminal_type, clamps_per_side).
Inputs: project_id (required), block, subsystem, terminals, +2 more.
allow_multiple_wiresAllow multiple wires on a terminalA
Let one device terminal take several wires in this project (e.g. a two-level terminal), silencing its fan-out. allow=false reverts.
Inputs: terminal (required), project_id (required), allow.
clear_block_positionsClear block positionsADestructive
Unpin every block in one view so it goes back to auto-layout. Other views keep theirs.
Inputs: project_id (required), subsystem.
create_projectCreate projectA
Create a new project (Free plan: max 3, always public). sample=true starts from the sample project (the Arduino Parking Sensor template). Pass team (name or id) to create it in a team or class: it starts private to you and the team's owner/admins; share it from Ohmstead.
Inputs: title (required), team, sample.
explain_sizingExplain sizingARead-only
One wire's sizing breakdown — current, design current, gauge, ampacity and its derating, voltage drop, the fuse or breaker behind it, and the suggested gauge — the same numbers the wire's details show in Ohmstead. Find the wire by id, or by its ends like update_connection takes them.
Inputs: project_id (required), to, from, connection_id.
export_project_fileExport project fileARead-only
The project as an Ohmstead project file (.ohmstead): plain text, one line per part and wire, sorted, addressed by tag, with drag positions and draw order in the last section. Commit it to Git or edit it and bring it back with import_project_file. Lines starting with # at the top list references that were left out because what they point at no longer exists.
Inputs: project_id (required).
fix_fanoutsFix fan-outsA
Route every fan-out through terminal strips (one strip per electrical net, jumpered as needed), same as the app's "Fix all". New strips use the project default block (update_project default_block); protective-earth fan-outs get the PE block (default_pe_block, else a generic PE block). terminal_type only applies to generic blocks.
Inputs: project_id (required), terminal_type.
fork_partFork Codex partB
Copy a built-in or community part into your own Codex so you can edit it.
Inputs: part_id (required).
get_projectGet projectCRead-only
A project's subsystems, components (tag → Codex part), P&ID items and lines, wires (grid rows) and current issues. Set format=json for the raw document.
Inputs: project_id (required), format.
import_project_fileImport project fileA
Read an Ohmstead project file (.ohmstead text). With project_id it goes over that project: components, subsystems and wires keep their ids by tag, so saved positions and embeds survive. Without apply it only reports what would change (always do that first and show the user); apply=true saves. Without project_id it makes a new project named title (Free plan: max 3). Parts resolve by id, then by maker and number; anything missing or ambiguous is named and nothing is saved.
Inputs: text (required), team, apply, title, +1 more.
import_wiring_listImport a design (wire list, BOM, or a drawing you read)A
Import an existing design into a NEW Ohmstead project. Sources: rows you extracted yourself (read an EPLAN / SKYCAD / AutoCAD Electrical / SolidWorks Electrical PDF page by page: devices with tags + part numbers from the parts list, wires as TAG:TERMINAL pairs from the cross-references / wire numbers, strips with their terminal order from the terminal diagrams), and/or CSV text: wire_csv (connection / wire list export) and bom_csv (BOM / parts list). Devices are matched to the Codex by part number; unknown part numbers are PROPOSED, never created unless listed in accept_parts. BOM lines no wire touches and no Codex part matches (enclosure, hardware) are listed, not placed. Strip numbers are imported locked. level: as-drawn (strips exactly as imported), light (pack, numbers kept), split-pack (split by subsystem + function, pack, numbers kept), full (split, pack, renumber). Device connections are checked to stay identical. Devices with no subsystem hint get PROPOSED subsystems from strip function and how they connect (Power, Control, field groups, areas from numbered tags), never applied unless listed in accept_subsystems; to change one, set subsystem on those device rows and run the dry run again. apply=false (default) returns the report only; show it to the user and ask before applying.
Inputs: title (required), team, apply, level, +9 more.
layout_viewLayout of a viewARead-only
Run the schematic layout for one view (the project, or a subsystem's drill-down) and list every block's position and size and every print page's frame, so blocks and pages can be placed without guessing. Block x, y are relative to the block's own subsystem (what set_block_positions takes); ax, ay are absolute in the view (what pages use). Pages are a fixed 1504 × 800 frame; automatic pages (auto:0, auto:1…) cover whatever no placed page holds. Takes a few seconds, up to ~15 s on a large project.
Inputs: project_id (required), subsystem.
link_instrumentLink instrumentA
Link a P&ID item to a wiring component by tag, or clear the link with component null. The project's tag rule decides which tag the item prints, and the result shows it.
Inputs: item (required), component (required), project_id (required).
list_manufacturersList manufacturersCRead-only
Manufacturers available for Codex parts.
Inputs: no named parameters.
list_pid_symbolsList P&ID symbolsBRead-only
P&ID symbols by group: key, label, base size, whether it resizes, and its ports with their x,y offset from the item's centre at that size. A resized item's ports are listed when it is added.
Inputs: no named parameters.
list_projectsList projectsARead-only
The user's Ohmstead projects, newest first. Personal workspace by default; pass team (name or id, see whoami) for that team's projects you can see.
Inputs: team.
list_signal_typesList signal typesARead-only
Signal types (name, category, wire color, gauge, volts) available for terminals and wires.
Inputs: no named parameters.
optimize_stripsOptimize terminal stripsA
Re-pack terminal strips to the fewest terminals: each net becomes one jumpered run sized to its wires (block capacity), empty spares go, like signals sit together, unlocked terminals are renumbered 1..n (locked ones keep their numbers). Multi-level and diode/LED blocks, cabled nets, and nets whose wires don't fit a run's clamp range (block wire_mm2) are left as they are. With spare_terminal_pct set (update_project), each packed strip ends with that share of its used terminals as empty spare terminals. Device connections never change. apply=false (default) only reports the before/after counts; ask the user before applying, since terminal numbers change.
Inputs: project_id (required), apply, strip.
remove_cableRemove cableADestructive
Remove a cable and its conductors from a project (the connectors stay on their parts). A terminal-end cable's conductors stay as loose wires. This edits the project; it never deletes projects or Codex parts.
Inputs: cable (required), project_id (required).
remove_componentsRemove componentsADestructive
Delete components (devices or terminal strips) by tag, with every wire and cable on them. Modules in a removed PLC's rack come out of it; linked P&ID items stay and are unlinked. Nothing is deleted if any tag is unknown.
Inputs: tags (required), project_id (required).
remove_connectionsRemove wiresBDestructive
Remove wires (grid rows) from a project by id. This edits the project; it never deletes projects or Codex parts.
Inputs: project_id (required), connection_ids (required).
remove_pageRemove print pageADestructive
Remove a placed print page (id or name). Its blocks stay where they are and print on automatic pages.
Inputs: page (required), project_id (required), subsystem.
remove_pid_itemsRemove P&ID itemsADestructive
Remove items from the P&ID, and every line touching them. Linked wiring components stay in the schematic.
Inputs: items (required), project_id (required).
remove_pid_sheetRemove P&ID sheetA
Remove a placed P&ID sheet by id or name. Its items stay on the drawing and move to the automatic sheets.
Inputs: sheet (required), project_id (required).
remove_process_linesRemove process linesADestructive
Remove lines from the P&ID by id (get_project lists them). Signal lines derived from the wiring aren't stored here; change the wiring to change them.
Inputs: lines (required), project_id (required).
remove_subsystemRemove subsystemADestructive
Delete a subsystem. Nothing else is deleted: its components and child subsystems move up to its parent (or the top level).
Inputs: subsystem (required), project_id (required).
save_partCreate or update Codex partA
Create a Codex part, or update one you own (pass part_id). A part must be complete: name, manufacturer, part number, category, description and at least one terminal (accessory parts, block.kind accessory, need none). Terminal blocks (category terminal) carry block data and per-terminal level/side; terminals can carry load_a / rated_a current data, and protective parts (fuse, breaker) list their allowed trip_ratings. Passive parts (category resistor, capacitor, inductor or diode) with exactly two terminals and no connectors draw on the schematic as inline glyphs, not blocks. Ask the user for datasheet values rather than guessing. On update the terminal list REPLACES the existing one, so include every terminal (use add_part_terminals to just add some). Free users' parts are always public; Pro parts default to private. Pass team (name or id) to create it in that team's Codex (team-only; any editor in the team can edit it later). A part using one of your own signal types in a team needs that signal type in the team too.
Inputs: name (required), category (required), description (required), part_number (required), +9 more.
save_signal_typeCreate or update a signal typeA
Create a signal type (what a wire carries and the color it draws in), or update one you own (pass signal_id). Comms types draw dashed and let a terminal take several wires without a fan-out. Free users' signal types are always public; Pro ones default to private. Built-in types are read-only.
Inputs: name (required), color (required), awg, mm2, +8 more.
search_codexSearch CodexBRead-only
Search the parts library (built-in, community and yours) by name, part number, manufacturer, description or terminal name.
Inputs: limit, query, category, mine_only, +1 more.
set_block_positionsSet block positionsA
Pin blocks (components, terminal strips or subsystems) at positions in one view, instead of where auto-layout puts them. x, y are the block's top-left, relative to its own subsystem in that view (layout_view shows current values). Unpinned blocks keep laying out automatically. Wires reroute in the app.
Inputs: blocks (required), project_id (required), subsystem.
set_strip_blocksSet strip terminal blocksA
Set the terminal block part of strip terminals (a range by label, or all). Wires keep their level: bare labels become level A on a multi-level block and back. Refused if wires sit on a level the new block doesn't have. block = part id or part number; omit (null) to return the terminals to the strip default.
Inputs: strip (required), project_id (required), to, from, +1 more.
set_strip_partsOverride strip part quantitiesA
Override how many of a part a strip needs (accessories: end plates, end stops, jumper bars, markers, or any extra part). Ohmstead works these out from the blocks; an override replaces that count (0 removes the part). qty null = back to the worked-out count. Block counts can't be overridden; change the terminals instead.
Inputs: parts (required), strip (required), project_id (required).
split_stripsSplit terminal strips by subsystem / functionA
Split strips so each serves one subsystem and/or one function: power (TB-PWR), PE (TB-PE), AC (TB-AC), field I/O per PLC module (TB-IO); the rest stays on plain TB strips. Everything tied together on a strip moves as one unit; a unit serving several subsystems goes to their common parent (shared distribution at the level above). Wires move with their terminals; device connections never change. apply=false (default) reports the plan; ask the user before applying. pack=true also re-packs the results (like optimize_strips).
Inputs: project_id (required), by, pack, apply, +1 more.
update_cableUpdate cableA
Change a cable by tag or id: retag, spec, gauge, length, either end (the pin map resets to 1:1), replace the whole pin map (conductors), reset it (reset_pin_map), or set the draw mode. Omitted fields stay the same.
Inputs: cable (required), project_id (required), to, draw, +7 more.
update_componentsUpdate componentsA
Retag a component, relink it to another Codex part, move it into a subsystem (subsystem: name/id, or "" for top level), put an I/O module in a PLC slot (plc + slot; a module already in that slot is taken out), or set a fuse/breaker's trip rating (trip_a; must be one of the part's allowed ratings when it lists any). Identify by current tag.
Inputs: changes (required), project_id (required).
update_connectionUpdate wireA
Change one wire (grid row) by id: either end, signal, note, draw mode, gauge, bundle tag, or length (in the project's unit; null clears). Omitted fields stay the same; note "" clears it, gauge "" goes back to the signal type's gauge, bundle "" clears the tag.
Inputs: project_id (required), connection_id (required), to, draw, +6 more.
update_harnessUpdate harnessA
Overrides for a harness: all loose wires between the same two subsystems (or a subsystem and a terminal strip), worked out automatically and drawn as one trunk with a tag (H1, H2…). get_project lists them. Retag, name it, draw it as a trunk or as separate wires, everywhere or in one view, or change its minimum wire count. null clears a field back to automatic. The project-wide minimum is update_project harness_min.
Inputs: harness (required), project_id (required), name, show, +6 more.
update_pageUpdate print pageA
Rename or move a print page. page: id or name of a placed page, or an automatic page "auto:0", "auto:1"… (with subsystem for a drill-down view; automatic pages can only be renamed, and an empty name gives back the automatic one).
Inputs: page (required), project_id (required), x, y, +2 more.
update_pid_itemsUpdate P&ID itemsA
Change placed P&ID items without touching their lines: position, size, symbol, tag, location, props. Lines keep their spot through a resize or symbol change. A tag follows the project's tag rule: renaming an item linked under the "same" rule renames its wiring component too. A blank location unsets it, and so does a blank props field.
Inputs: items (required), project_id (required).
update_pid_sheetUpdate P&ID sheetA
Rename a placed P&ID sheet, move its frame (x,y is the top-left), or change where it prints (position, 1 = first). sheet is its id or name. The result lists what each sheet holds.
Inputs: sheet (required), project_id (required), x, y, +2 more.
update_projectUpdate project settingsB
Rename, change status/visibility (Pro/Student only for private), default signal flow, title block fields, the sizing standard and its ampacity column, the length unit, the voltage-drop limits, or the spare-terminal percentage. title_block keys are the PDF template's field ids (built-in: drawingNo, drawnBy, customer, rev; custom template fields have their own ids).
Inputs: project_id (required), flow, title, status, +20 more.
update_subsystemUpdate subsystemA
Rename a subsystem, move it under another parent (parent: name/id, or "" for top level; its components and child subsystems come with it), or change its signal flow.
Inputs: subsystem (required), project_id (required), flow, name, +1 more.
validate_projectValidate projectARead-only
Check a project for fan-outs (too many wires on a terminal), signal clashes (different signal types on one net), incomplete rows, missing signals, and terminals/parts that don't exist. Also reports supply overloads, wires outside their terminal block's clamp wire range, and sizing findings (wire too small, below the minimum size, fuse too big, missing fuse rating, voltage drop over the limit) with suggested values from the project's sizing standard.
Inputs: project_id (required).
whoamiWho am IARead-only
The signed-in Ohmstead user, plan, and the teams and classes they're in (with their role).
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Generate 12V/24V/48V wiring diagrams and size wires, fuses, batteries, solar, and inverters.
Plan DC electrical systems: find components, calculate circuits, check designs and create drafts.
Electrical single-line and multi-line diagrams: build, check (NF C 15-100, IEC 60364), draw, PDF.
Design, route, check, review and export manufacturable PCBs from plain language; KiCad import.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI tools to create, edit, and inspect KiCAD schematic files, including components, wires, labels, and sheets.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with KiCAD for PCB design automation. Users can design PCBs using natural language, including component placement, routing, checks, and export.1MIT
- AlicenseBqualityCmaintenanceEnables creating and editing KiCad projects through natural language, including scaffolding projects, placing schematic symbols, wires and labels, and adding PCB footprints, tracks and nets. It also runs ERC/DRC checks and exports to PDF, SVG, netlist, BOM, STEP, DXF, gerbers and drill files via kicad-cli.141MIT
- AlicenseNot gradedqualityBmaintenanceEnables an LLM agent to assemble, wire, run, fault and observe electromechanical motor-control circuits through 26 tools covering component placement, terminal connections, button/switch operation, fault injection, and simulation control. Also lets agents load and save circuits and generate PDF drawing sets, screenshots and scripted demo videos.MIT