Skip to main content
Glama
ohmstead-mcp

ohmstead-mcp

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Ohmstead is electrical CAD software for wiring schematics: the project is data (parts and wire rows) and the drawing is generated from it.

Model:

  • A project has components (device instances with a unique tag like PLC_MAIN, PSU1, K1), each linked to a Codex part.

  • The Codex is the shared parts library. A part has a name, manufacturer, part number, category, description and terminals (each with a terminal type, a default signal type, and optional load_a / rated_a current in A; protective parts also list their allowed trip ratings). Parts are only created in the Codex (save_part), never invented inside a project. Signal types too (save_signal_type); check list_signal_types first. Search before creating; built-in and community parts can be forked.

  • Wires are grid rows: "FROM_TAG:TERMINAL" → "TO_TAG:TERMINAL" with a signal type (e.g. 24VDC (+), 0VDC (-), Protective Earth). If no signal is given, the From terminal's Codex default is used.

  • A device terminal takes one wire unless its Codex terminal allows more (max_wires), the user allowed it, or all wires are comms (daisy-chain). Extra wires are a "fan-out": route them through a terminal strip (TB1, TB2…) with fix_fanouts. Strips are project-level, not Codex parts; their terminals are created on demand.

  • Terminal blocks: Codex parts with category terminal can carry block data (kind, width, wire range, ratings, jumper style, accessory parts) and per-terminal level (A/B/C) and side (in/out). End plates, end stops, jumper bars and markers are accessory parts (block.kind accessory, no terminals). On a strip, each terminal is a block (strip default, project default or a generic block); multi-level blocks are addressed with a level letter: TB1:4A, TB1:4B. Set the project's default block and PE block with update_project (default_block, default_pe_block); fix_fanouts and add_terminal_strip use them. Change blocks on existing terminals with set_strip_blocks. A block's wire range is enforced: validate_project flags wires whose gauge is too big or small for the clamp they land on, and packing leaves such nets where they are. Packing can append spare terminals: update_project spare_terminal_pct sets how many, as a % of each strip's used terminals.

  • Subsystems group components and can nest; each has a signal flow (LR or TB). update_subsystem renames one, moves it under another parent or changes its flow; remove_subsystem deletes it and moves its contents up a level. update_components moves components between subsystems; remove_components deletes them with their wires.

  • Connectors: a Codex part's terminals can be grouped into named connectors (X1, X2…), each pin with its own type and default signal, plus gender (male/female) and keying (e.g. M12 A). A pin is addressed "TAG:X1.3" in wires. Give terminals a connector in save_part / add_part_terminals.

  • Harnesses (H1, H2…): all loose wires between the same two subsystems, or a subsystem and a terminal strip, draw as one trunk line once there are enough of them (update_project harness_min, default 3). They are worked out from the wiring; get_project lists them and update_harness sets overrides. A wire set to draw as a reference stays one.

  • Cables (W1, W2…) join two connectors pin for pin (add_cable). Pins map 1:1 by default (same pin names, else pin order); each conductor is its own row with a signal and an optional conductor color (BN, WH, BU…). Edit with update_cable. Validation flags mated ends with the same gender or different keying. Loose wires may still land on single pins.

  • PLC racks: a PLC part (category plc) can have module slots (slot_count). I/O modules are separate Codex parts (category io). In a project, put a module in a PLC slot with update_components (plc + slot).

  • Sizing: projects pick a sizing standard (NEC by default, NFPA 79, ABYC E-11 DC for vehicles, vans and boats, or Low-voltage electronics for dev boards, breakouts and header pins), an ampacity column and an ambient temperature (update_project sizing_standard / sizing_column / ambient_c, default 40 °C); validate_project reports wires too small for their current, minimum sizes and fuse ratings with suggested values, from tables labelled "unverified tables" until the owner checks them. Ampacity is derated for bundling: the conductors of a cable count together, and loose wires sharing a bundle tag (add_connections / update_connection bundle) do too. Voltage drop (set lengths on wires and cables in the project's length unit, volts and phases on signal types, and the drop limits with update_project) is checked along each wire's run to the supply and flags wires over the branch or total limit; explain_sizing walks through any one wire's numbers (current, derating, drop, the fuse behind it, the suggestion).

  • P&ID: a project can carry a process view of the same document. Items are symbols from list_pid_symbols (add_pid_items); process lines join them (add_process_lines); update_pid_items moves, resizes or retags a placed item and its lines stay on. Ports are named by angle in the symbol's own frame, clockwise from up: 0, 90, 180, 270, and 90.1, 90.2 on a side with several. link_instrument ties an item to a wiring component, and the project's tag rule decides which tag it prints. An instrument's signal lines are derived from the wiring, so never add them by hand: wire the component and they appear. A hand-drawn signal line is only for something not wired yet, and validate_project flags it once the wiring disagrees. For words on the drawing use symbols note.text and area.frame, with the words as the tag and an at position: a note wraps to its width, an area is a labelled outline behind the drawing (room boundaries, skids) that prints on every sheet it crosses, and neither takes lines. add_pid_sheet places a named print sheet: a fixed frame that prints the items whose centres it holds; everything else tiles onto automatic sheets.

  • Schematic layout and pages: the drawing lays out automatically unless blocks are pinned. layout_view shows a view's blocks (position, size) and print pages; set_block_positions pins blocks, clear_block_positions unpins a whole view. A print page is a fixed-size frame placed in a view (add_page, update_page, remove_page); blocks whose centre is inside print on it, and everything else tiles onto automatic pages (auto:0, auto:1…), which update_page can name. Each subsystem's drill-down is its own view (subsystem).

  • Import: import_wiring_list turns an existing design (a PDF you read page by page, a wire-list CSV, a BOM) into a new project; dry run first, then apply after the user agrees.

  • Layout, routing and PDF are automatic in the app; the user opens the project in Ohmstead to see the drawing.

Workflow: list_projects / get_project → search_codex → add_components → add_connections → validate_project → fix_fanouts. Report issues to the user rather than guessing; ask before creating Codex parts with uncertain terminal data. Changes are saved straight to the database. If the project is open in Ohmstead, the user should reload it to see them.

  • Teams and classes: whoami lists the user's teams and their role (classes say instructor / TA / student / viewer). list_projects, create_project, save_part and import_wiring_list take an optional team (name or id); every other tool follows the project's team. A team project is visible to its creator, the team's owner/admins and members it's shared with. Submitted / issued (locked) projects are read-only, and so is a project a teammate has open for editing in Ohmstead (whichever side — schematic or P&ID — they're on). Using one of your private parts in a team project copies it into the team Codex. On the Free plan only the read-only tools are available; edits need Pro or Student (whoami shows the plan). A Free user who is an editor/student or up in an active team or class can still edit that team's projects and Codex.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
whoamiA

The signed-in Ohmstead user, plan, and the teams and classes they're in (with their role).

list_projectsA

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.

get_projectC

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.

export_project_fileA

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.

import_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.

create_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.

update_projectB

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).

add_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.

update_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.

remove_componentsA

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.

add_subsystemB

Create a subsystem (group) to organize components, optionally nested under a parent subsystem, with its own signal flow.

update_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.

remove_subsystemA

Delete a subsystem. Nothing else is deleted: its components and child subsystems move up to its parent (or the top level).

layout_viewA

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.

set_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.

clear_block_positionsA

Unpin every block in one view so it goes back to auto-layout. Other views keep theirs.

add_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.

update_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).

remove_pageA

Remove a placed print page (id or name). Its blocks stay where they are and print on automatic pages.

add_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).

set_strip_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.

optimize_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.

split_stripsA

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).

set_strip_partsA

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.

add_connectionsA

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.

update_connectionA

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.

remove_connectionsB

Remove wires (grid rows) from a project by id. This edits the project; it never deletes projects or Codex parts.

add_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…

update_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.

update_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.

remove_cableA

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.

add_pid_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.

update_pid_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.

add_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.

link_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.

remove_pid_itemsA

Remove items from the P&ID, and every line touching them. Linked wiring components stay in the schematic.

remove_process_linesA

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.

add_pid_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.

update_pid_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.

remove_pid_sheetA

Remove a placed P&ID sheet by id or name. Its items stay on the drawing and move to the automatic sheets.

list_pid_symbolsB

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.

validate_projectA

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.

explain_sizingA

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.

fix_fanoutsA

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.

allow_multiple_wiresA

Let one device terminal take several wires in this project (e.g. a two-level terminal), silencing its fan-out. allow=false reverts.

search_codexB

Search the parts library (built-in, community and yours) by name, part number, manufacturer, description or terminal name.

list_signal_typesA

Signal types (name, category, wire color, gauge, volts) available for terminals and wires.

save_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.

list_manufacturersC

Manufacturers available for Codex parts.

save_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.

add_part_terminalsA

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.

fork_partB

Copy a built-in or community part into your own Codex so you can edit it.

import_wiring_listA

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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 53 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count2/5

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.

Completeness4/5

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

ActivityMaintained
ResponsivenessNo recent community issues