Debug Probe MCP Server

MCPOpen SourceMIT29.0

by es617 • Uncategorized

A stateful debug probe MCP server enabling AI agents and developer tools to interact with embedded targets via debug probes.

Example Use Cases

1
Flash and debug embedded firmware interactively and conversationally.
2
Inspect and manipulate memory and peripheral registers with symbol and register-level awareness.
3
Automate test sequences and manage multiple debug probes simultaneously.

Description

This MCP server provides a backend-agnostic interface to control on-chip debug probes like SEGGER J-Link, allowing AI agents and developer tools to flash firmware, debug, inspect memory, and manage breakpoints conversationally. It supports symbol-aware debugging with ELF files, register-level access with SVD files, and real-time logging via RTT. The server facilitates faster iteration, automation of test flows, and multi-probe setups, improving embedded development workflows.

Capabilities(41 total)

Tools (41)

dbgprobe.probes.list

List attached debug probes. Returns vendor/backend-specific info (serial number, description). For J-Link, enumerates via JLinkExe.

backend:string

dbgprobe.connect

Establish a debug probe session. Returns a session_id and the resolved configuration (backend, executable paths, defaults applied). The target is halted after connecting — this is inherent to the debug probe connection. Use dbgprobe.go to resume execution if needed. For symbol-aware debugging, attach an ELF file with dbgprobe.elf.attach after connecting — this enables breakpoints by function name and address-to-symbol resolution in status/step/halt responses. For register-level peripheral access, attach an SVD file with dbgprobe.svd.attach.

backend:stringprobe_id:stringdevice:stringinterface:stringspeed_khz:integerstring

dbgprobe.erase

Erase target flash. With no address params: full chip erase (unlocks secured/read-protected devices like Nordic APPROTECT). With start_addr and end_addr: erase only that range. If session_id is provided, erases through the active GDB session (preferred — no USB contention). Without session_id, uses JLinkExe directly (for session-less erase, e.g. unlocking a secured device before connect).

session_id:stringbackend:stringprobe_id:stringdevice:stringinterface:stringspeed_khz:integerstringstart_addr:integerstringend_addr:integerstring

dbgprobe.disconnect

Close a debug probe session and release resources.

session_id:string*

dbgprobe.reset

Reset the target. Modes: 'soft' (default) — software reset and resume, 'hard' — hardware reset, 'halt' — reset and halt at first instruction.

session_id:string*mode:string

Quick Actions

View on GitHub

Security

Scanned 27 days ago

Risk Level

MINIMAL

Read-only data retrieval, no side effects

Trust Score

C55/100

8/17 checks passed

Scores are informational only and provided “as is” without warranty. AgentHotspot assumes no liability for actions taken based on these ratings.

Quick Stats

Service TypeMCP

Pricing ModelFree

Capabilities41 Tools / 0 Prompts / 0 Resources

Owneres617

CategoryUncategorized

DependenciesStandalone

Set Your Username