Dbgprobe Mcp Server
Let your coding agent flash firmware and peek at MCU memory through a J-Link (or future probe backends) without leaving the MCP session.
Overview
io.github.es617/dbgprobe-mcp-server is a MCP server for the Ship phase that lets AI agents connect to debug probes, flash firmware, and read or write target memory.
What is this MCP server?
- Connect to debug probes and perform flash, memory read/write, and target reset from MCP tools
- J-Link backend by default with DBGPROBE_BACKEND and auto-detected JLinkExe paths
- Per-session overrides via DBGPROBE_JLINK_DEVICE for targets like nRF52840_xxAA
- Structured logging levels through DBGPROBE_MCP_LOG_LEVEL
- Stdio PyPI package dbgprobe-mcp-server at version 0.1.4
- Package version 0.1.4 on PyPI as dbgprobe-mcp-server
- Default debug backend jlink via DBGPROBE_BACKEND
- Documented J-Link path, GDB server, device, and interface environment variables in server metadata
Community signal: 6 GitHub stars.
What problem does it solve?
Firmware validation stalls when only you can operate J-Link commands while the agent lacks a safe, structured path to the probe.
Who is it for?
Embedded indie devs with J-Link hardware on the desk who want agent-assisted debug sessions during test and release prep.
Skip if: Pure web or mobile builders without physical targets, or teams forbidden from automated memory writes on production units.
What do I get? / Deliverables
Once configured, your agent can run documented probe operations so flash-verify and memory inspection become repeatable MCP tool calls.
- Probe connection and flash operations callable by the agent
- Memory read/write and reset tooling for bench validation
- Configurable backend and device strings for repeatable sessions
Recommended MCP Servers
Journey fit
Probe-assisted flash-and-inspect work sits in ship when you validate binaries on silicon before you call a board truly release-ready. Memory read, reset, and flash checks are hardware-in-the-loop testing activities, not greenfield feature coding.
How it compares
Probe-facing MCP integration, not a cloud CI flash service or a generic serial console.
Common Questions / FAQ
Who is io.github.es617/dbgprobe-mcp-server for?
It is for firmware-focused solo builders and small teams who use J-Link (today) and want MCP tools for flash, memory, and reset on real silicon.
When should I use io.github.es617/dbgprobe-mcp-server?
Use it while hardware-in-the-loop testing—after you have a binary—to confirm programming, inspect memory, and recover bricked dev boards under controlled conditions.
How do I add io.github.es617/dbgprobe-mcp-server to my agent?
Install dbgprobe-mcp-server 0.1.4 from PyPI, set DBGPROBE_JLINK_PATH and DBGPROBE_JLINK_DEVICE if needed, register the stdio MCP server in your host, and connect the probe before invoking tools.