Is there a PlatformIO MCP server?

Yes. jl-codes/platformio-mcp wraps PlatformIO to list, build, flash and monitor boards, and says it covers more than 1,000 boards across 30+ platforms. It had 51 GitHub stars and a push on 2026-09-09 when it was surveyed on 2026-09-16.

Why use this server instead of platformio-mcp?

If PlatformIO already builds your projects, platformio-mcp may be the better fit, because it is built around that toolchain. This server's build_project tool runs pio run and returns parsed diagnostics, proven so far against recorded PlatformIO output rather than a real install. Beyond building, its 21 tools cover boards, flashing, serial, GPIO, ADC, PWM, I2C and SPI over MicroPython or a bridge sketch, a BOOTSEL copy that needs no tool at all for the Pico, and a phone bridge for Bluetooth LE boards, which none of the surveyed servers had. None of it has been run on a physical board by the studio yet.

Doesn't Espressif ship its own MCP server?

ESP-IDF v6.1 includes idf.py mcp-server. When surveyed on 2026-09-16 it had an open bug, esp-idf issue 19087, where print output to stdout corrupts the JSON-RPC stream that stdio MCP clients depend on.

Which server should I use for SWD debugging and breakpoints?

Not this one. embedded-debugger-mcp covers probe-rs and OpenOCD work such as halting cores, hardware breakpoints, memory access and RTT, and it had 190 stars when surveyed. This server talks to boards over their serial port only.

How many microcontroller MCP servers exist?

The survey on 2026-09-16 found 32 MCP servers for embedded, serial or hardware work on GitHub. None of them had a phone component, and none paired a desktop server with a Bluetooth bridge app.

PlatformIO and other microcontroller MCP servers, compared

Several open-source MCP servers already let an agent flash and talk to a microcontroller. This page lists the ones found in a GitHub survey on 2026-09-16, with star counts and last-push dates as recorded that day, and says plainly where this server is different and where another one is the better choice.

Last checked against the source code on 2026-09-20.

The servers surveyed

Project	Stars	Last push	What it does
jl-codes/platformio-mcp	51	2026-09-09	PlatformIO wrapper: list, build, flash, monitor; claims 1,000+ boards on 30+ platforms
horw/esp-mcp	157	2025-12-27	ESP-IDF build, flash and port listing; its README calls it a proof of concept, and monitoring is listed as future work
Espressif idf.py mcp-server (ESP-IDF v6.1)	first-party	open bug	The vendor's own entry point; open issue 19087 reports stdout prints corrupting the stdio JSON-RPC stream
hardware-mcp/arduino-mcp-server	18	2026-08-22	arduino-cli wrapper for compile, upload and serial monitor, plus electrical preflight checks
mixelpixx/arduino-mcp	21	2026-07-28	A fork of Arduino IDE 2.x with MCP built into the IDE
es617/serial-mcp-server	20	2026-03-07	Serial toolset with DTR/RTS control and PTY mirroring for screen or minicom
qarnet/serial-mcp	9	2026-09-15	Rust, stdio and HTTP, 25 serial tools with framing helpers; listed on the official MCP Registry
Adancurusul/embedded-debugger-mcp	190	2026-07-16	probe-rs / OpenOCD debugging: flash, halt, step, breakpoints, memory, RTT, Cortex-M fault diagnosis
shieldyguy/stm32-mcp	25	2026-08-13	Build, flash and debug STM32 over SWD and serial
matta-pie/micro-mcp	1	2026-02-01	An MCP server written in MicroPython that runs on the board itself

Figures as recorded on 2026-09-16. Star counts and activity change daily; follow the links for current numbers. None of these projects had a mobile component.

Where this server is different

One tool surface for three families. 21 tools cover the ESP32 family, the Raspberry Pi RP2040/RP2350 and the Arduino Uno R4: list_boards, flash_firmware, four serial tools with an always-on monitor buffer, GPIO, ADC, PWM, I2C and SPI tools that ride MicroPython's REPL or a bridge sketch, mpy_exec, board_reset, and compile_sketch and build_project over arduino-cli and PlatformIO. The pin and bus tools are proven against the real MicroPython interpreter in a simulator and have not been run on a physical board yet.
A Pico needs no tool to flash. When picotool is absent, the server copies the UF2 file to the BOOTSEL drive.
Loud failures. A missing CLI returns the install command, an unknown family is an error, and a half-configured bridge is a named warning. None of them comes back as an empty success.
A phone bridge. With Pro, a Bluetooth LE board that speaks the Nordic UART Service can be reached through the companion app. See the bridge guide.
One price. The server is free; the Pro unlock is a single $20 payment.

Where another server is the better choice

You build with PlatformIO across many boards and want a server designed around it: platformio-mcp is that. build_project here runs pio run for any PlatformIO project, but it has been proven against recorded output only, not a real PlatformIO install.
You need SWD debugging, breakpoints or RTT: embedded-debugger-mcp does that. This server does not debug through a probe.
You work on STM32: this server does not enumerate or flash STM32 boards, and its PlatformIO build tool has never been run against one; stm32-mcp targets them.
You need serial framing helpers such as Modbus ASCII or SLIP, or an HTTP transport today: qarnet/serial-mcp has them, and this server does not.

What the embedded crowd says about AI and hardware

The founders of Embedder, a funded company building an agent for embedded work, described the problem in their launch post (Launch HN, 2025-08-15):

"we'd ask Cursor to, say, write an I2C driver for a new sensor on an STM32, and it would confidently spit out code that used non-existent registers or HAL functions from the wrong chip family."

Letting the agent flash the board and read what it prints is not a full answer to that, but it replaces a guess with an observation. Start with the quickstart.

Frequently asked questions

Is there a PlatformIO MCP server?: Yes. jl-codes/platformio-mcp wraps PlatformIO to list, build, flash and monitor boards, and says it covers more than 1,000 boards across 30+ platforms. It had 51 GitHub stars and a push on 2026-09-09 when it was surveyed on 2026-09-16.
Why use this server instead of platformio-mcp?: If PlatformIO already builds your projects, platformio-mcp may be the better fit, because it is built around that toolchain. This server's build_project tool runs pio run and returns parsed diagnostics, proven so far against recorded PlatformIO output rather than a real install. Beyond building, its 21 tools cover boards, flashing, serial, GPIO, ADC, PWM, I2C and SPI over MicroPython or a bridge sketch, a BOOTSEL copy that needs no tool at all for the Pico, and a phone bridge for Bluetooth LE boards, which none of the surveyed servers had. None of it has been run on a physical board by the studio yet.
Doesn't Espressif ship its own MCP server?: ESP-IDF v6.1 includes idf.py mcp-server. When surveyed on 2026-09-16 it had an open bug, esp-idf issue 19087, where print output to stdout corrupts the JSON-RPC stream that stdio MCP clients depend on.
Which server should I use for SWD debugging and breakpoints?: Not this one. embedded-debugger-mcp covers probe-rs and OpenOCD work such as halting cores, hardware breakpoints, memory access and RTT, and it had 190 stars when surveyed. This server talks to boards over their serial port only.
How many microcontroller MCP servers exist?: The survey on 2026-09-16 found 32 MCP servers for embedded, serial or hardware work on GitHub. None of them had a phone component, and none paired a desktop server with a Bluetooth bridge app.