Proteus MCP
Related Servers
Alternatives to Proteus MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables an AI or MCP-compatible client to read and edit a live Altium Designer session in place, with optional KiCad and EasyEDA Pro backends, covering schematic, PCB, library, project, design-review, audit, and automation workflows.365Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents on Windows to edit 8051 C source, invoke Keil builds, load SHA256-verified HEX firmware into Proteus, and control simulation run, pause, and stop.MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-capable AI agents to generate and reorganize schematics, resolve LCSC components, place and route PCBs with custom DRC constraints, inspect design data, and safely apply, repair, or restore changes in native EasyEDA Pro and JLCEDA documents.219MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents end-to-end control of KiCad 9+ for rule checks, manufacturing exports, production-readiness certification, and live PCB editor control.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to drive KiCAD PCB design automation through MCP, covering schematic authoring, board and routing operations, footprint/symbol libraries, vendor PCB import, validation and DRC, and manufacturing export. It exposes 236 registered tools with keyword discovery, dynamic project-state resources, and optional Streamable HTTP transport with fail-closed Bearer authentication.MIT
- AlicenseNot gradedqualityDmaintenanceLocal Model Context Protocol server that exposes EasyEDA Pro design capabilities as MCP tools, enabling project inspection, schematic editing, PCB design, validation, and manufacturing exports through natural language.MIT
TDQS
Scored across 53 tools
Several tools target nearly identical territory and only deep description-reading separates them: native_read vs native_inspect vs live_read vs project_read all 'read the native project', simulation_sample vs simulation_observe vs simulation_log all sample simulator data, and four pcb_route* variants plus native_export vs native_apply vs native_export_led_chaser vs example_led_chaser are near-siblings. The detailed descriptions do provide the distinctions, but with 53 tools an agent is likely to misselect on the first pass (e.g. component_add vs circuit_edit vs live_edit vs native_set_component).
There is a systematic noun_verb prefix scheme (project_*, native_*, pcb_*, simulation_*, library_*, component_*, firmware_*), which is readable and groups well. But it mixes conventions with verb_noun outliers like connect_pins, export_svg, export_netlist, source_write, live_history, and one-off names like proteus_doctor and example_external_interrupt.
53 tools is far beyond a comfortable agent-facing surface, even for a broad proteus-automation domain spanning schematic, native file, PCB, simulation and manufacturing. Distinct capabilities here (e.g. four routing tools, three read tools, three status/diagnostic tools) could plausibly be consolidated into a single operation-dispatched tool.
Coverage is unusually deep: create/read/edit/validate/save/close/reopen for projects, add/set/connect/delete for circuits, plus exports, firmware build/inspect, simulation control/stimulus/observe, PCB read/route, and BOM. Minor gaps exist (no project delete/cleanup, explicitly no full ERC or Gerber/fabrication outputs), but these are declared boundaries rather than dead ends.