ohmstead-mcp
OfficialRelated Servers
Alternatives to ohmstead-mcp
No user-submitted related servers found.
Related Servers
- 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
- AlicenseBqualityBmaintenanceEnables natural-language generation of complete industrial electrical documentation—schematics, PLC I/O, PROFINET/IO-Link networks, terminal plans, cabinet layouts, BOM/cable/I/O lists—with configurable IEC/NFPA 79 validation and CADCraft export to DXF/PDF/PNG/DWG.41Apache 2.0
- 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

PCBEditor MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI assistants to turn plain-language requests into complete, routed and design-rule-checked printed circuit boards, including engineering review, part search and inventory use, and export to Gerber, KiCad, BOM and pick-and-place files.MIT- 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
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.