Dbgprobe MCP Server

Let AI agents interact with debug probes — connect, flash, read/write memory, and reset.

Local serverstdioPython

What is the Dbgprobe MCP Server?

Let AI agents interact with debug probes — connect, flash, read/write memory, and reset.

What it actually does

A stateful debug probe Model Context Protocol (MCP) server for developer tooling and AI agents. Works out of the box with Claude Code, VS Code with Copilot, and any MCP-compatible runtime. Communicates over stdio and drives on-chip debug probes (J-Link first, OpenOCD and pyOCD planned) to flash, debug, and inspect embedded targets.

  • Flash and iterate — — build firmware, flash it, reset, check behavior — all in one conversation
  • Inspect memory — — read peripheral registers, check RAM contents, verify flash writes
  • Debug interactively — — halt, step, set breakpoints, inspect state, resume
  • Automate test flows — — flash → reset → read output → validate
  • Multi-probe setups — — connect to multiple probes simultaneously, each with its own session

More MCP options

Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.

Maintainer setup documentation.

Configuration

VariableDescriptionRequired
DBGPROBE_JLINK_DEVICEConfiguration value read at startup.Optional
DBGPROBE_MCP_TOOL_SEPARATORConfiguration value read at startup.Optional
PULLConfiguration value read at startup.Optional
DBGPROBE_JLINK_PATHFilesystem location the server is allowed to use.Optional
DBGPROBE_JLINK_GDBSERVER_PATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • “Use Dbgprobe to Category.”
  • “Use Dbgprobe to Probe.”
  • “Use Dbgprobe to Introspection.”

Frequently asked questions

Let AI agents interact with debug probes — connect, flash, read/write memory, and reset. Confirm the tools offered by your installed version in the connected client. Tool availability and permissions depend on the server and account configuration.