uSimmics MCP Bridge
Related Servers
Alternatives to uSimmics MCP Bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables MCP-compatible agents to generate Qucs circuit schematics, run simulations, and parse results programmatically.2MIT
- AlicenseBqualityAmaintenanceEnables building wire-connected native schematics, visually checking them, editing values, and running native frequency/transient analyses plus symbolic formulas and plots, with results saved as CSV/PNG and openable in the separately installed application.29MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to create, read, update, and validate editable analog/RF circuit schematic projects (including a five-transistor OTA template), wiring and moving components by pin name, running topology checks, exporting SVG or SPICE/Spectre netlists and normalized JSON, and opening the browser editor with a project loaded. It also exposes the component library's exact pins and defaults so drawings stay netlist-correct.MIT
- AlicenseAqualityCmaintenanceA thin MCP server that wraps spicelib for circuit simulation. Exposes tools for running AC, transient, DC op, and parameter sweep analyses, enabling behavioral model fitting through iterative simulation and measurement comparison.48GPL 3.0
- AlicenseBqualityCmaintenanceEnables MCP-compatible AI clients to control CADFEKO, the FEKO solver, and POSTFEKO by running Lua API scripts, launching asynchronous jobs, monitoring progress, and exporting S11, impedance, Touchstone, model files, and images.91MIT
- AlicenseAqualityCmaintenanceEnables inspection and controlled modification of EasyEDA/LCEDA Pro designs through domain interfaces for schematics, PCBs, pins, netlists, DRC, auto-layout/routing, and Gerber/BOM/pick-and-place export.11Apache 2.0
TDQS
Scored across 21 tools
Most tools target clearly distinct operations: project setup, schematic CRUD, validation, simulation jobs, and result handling. A few boundaries require careful reading, especially run_schematic vs. start_job vs. parameter_sweep, and inspect_schematic vs. validate_schematic vs. read_schematic, but descriptions clarify them.
The set uses a mostly consistent snake_case convention, usually verb_noun (list_projects, read_schematic, save_schematic, cancel_job). Minor deviations are noun-first names like environment_status, job_status, and parameter_sweep, but the pattern remains readable.
At 21 tools, the surface is on the heavy side for a single MCP server, though the domain includes schematic editing, validation, rendering, simulation, job control, and templates. The count is defensible but borderline; some grouping could reduce cognitive load.
Coverage is strong: projects, templates, schematic build/read/save/clone/inspect/validate/preview/update, background jobs, sweeps, result comparison/publishing/reading, and environment checks are present. Minor gaps include no explicit delete/cleanup operation for projects or schematics and no dedicated artifact-listing tool.