hardware-tooling-mcp
Related Servers
Alternatives to hardware-tooling-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to directly inspect and debug embedded hardware: reading/writing serial ports and bus devices, auto-detecting baud rates, parsing Modbus/NMEA/custom binary frames, plus diagnosing failures through a 45-rule fault-pattern library, error-code tables, and compile/flash error translation. Also provides pin-conflict checking, register and Cortex-M fault decoding, pre-validated driver and component selection libraries, board knowledge, and guarded flashing with post-flash byte-level verification.59MIT
- FlicenseAqualityBmaintenanceEnables AI agents to compile, flash, erase, and read serial output from embedded development boards, with guardrails such as budget limits, serial port mutexes, and mandatory human confirmation for destructive operations.5-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Arduino boards for compiling, uploading sketches, and serial communication.6MIT
- AlicenseAqualityAmaintenanceLocal serial and USB hardware access for coding agents, with typed YAML protocol commands, checksum validation, audited writes, lossless captures, hardware-free replay, and MCP App visualizations. Runs locally over stdio; live hardware use requires a serial device connected to the same machine.187MIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to build, flash, debug, and communicate with STM32 microcontrollers over ST-Link entirely within the conversation. Provides headless CubeIDE builds, OpenOCD flashing, hardware breakpoints, live SWD variable monitoring resolved by C symbol names, fault triage, and pooled serial VCP I/O with deterministic sequencing for hardware-in-the-loop tests.35MIT
- AlicenseAqualityAmaintenanceEnables AI clients to compile and upload Arduino sketches, manage boards, cores, and libraries via arduino-cli, scaffold projects, and read serial output over stdio.261MIT
TDQS
Scored across 33 tools
Most tools target distinct hardware domains and actions: serial, FTDI/I2C/SPI, BLE, sigrok, audio/video, ADB, and process management. There are some overlaps, notably check_toolchains versus check_prerequisites, and compile_and_flash versus esptool_command/run_custom_toolchain, but the descriptions usually make the intended choice clear.
All tool names use consistent snake_case and are readable. The convention is mostly verb_noun, with domain-prefixed variants like ble_scan_devices and ftdi_i2c_transfer, plus a few noun-style names such as adb_command and esptool_command.
The server exposes 33 tools, which is heavy for a single MCP surface even though the underlying hardware-tooling domain is broad. Each domain is reasonably scoped, but the overall count exceeds the 25-tool threshold where tool selection and maintenance burden become significant.
The surface covers many major hardware workflows: serial monitoring, firmware build/flash, FTDI GPIO/I2C/SPI, BLE GATT, logic analysis, audio/video inspection, ADB, and process/port management. Minor gaps remain for native Linux I2C/SPI/GPIO access and direct JTAG/SWD operations, though generic process and custom-toolchain tools provide escape hatches.