Mmcp.market

Dbgprobe MCP server

by es617·io.github.es617/dbgprobe-mcp-server·v0.1.4·10 stars
No reviews yet

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

B75/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B75/100

full report

Adoption
New

10 stars27 downloads/wk

Reviews

Write one

Nobody has reviewed Dbgprobe yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Dbgprobe tools (15)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • dbgprobe.breakpoint.clear

    Clear a breakpoint at a target address.

  • dbgprobe.breakpoint.list

    List all active breakpoints for a session.

  • dbgprobe.disconnect

    Close a debug probe session and release resources.

  • dbgprobe.go

    Resume target execution (run/go).

  • dbgprobe.halt

    Halt the target CPU.

  • dbgprobe.rtt.status

    Return RTT status: active, bytes buffered, total read/written.

  • dbgprobe.rtt.stop

    Stop RTT and disconnect from the telnet port.

  • dbgprobe.spec.get

    Get the attached spec for a connection (returns null if none attached).

  • dbgprobe.spec.list

    List all registered specs with their metadata and matching hints.

  • dbgprobe.spec.read

    Read full spec content, file path, and metadata by spec_id.

  • dbgprobe.svd.list_fields

    List all fields for a register.

  • dbgprobe.svd.list_peripherals

    List all peripherals defined in the attached SVD.

  • dbgprobe.svd.list_registers

    List all registers for a peripheral.

  • dbgprobe.trace.status

    Return tracing config and event count.

  • dbgprobe.trace.tail

    Return last N trace events (default 50).

Public scan report

scanner v0.1.10 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan28 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 198 days ago4/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 75/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install Dbgprobe in Claude Code, Cursor or VS Code

claude mcp add dbgprobe-mcp-server -- uvx dbgprobe-mcp-server
Add to Cursor

What the publisher says

From the Dbgprobe repository's README, as published. We do not edit it. Read it on GitHub

Debug Probe MCP Server

<!-- mcp-name: io.github.es617/dbgprobe-mcp-server -->

<!-- TODO: add badges when backends are implemented --> <!-- --> <!-- -->

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.

Example: Let Claude Code list attached J-Link probes, connect to your nRF52840, flash a new firmware, read memory, and reset the target — all conversationally.

Demo

Video walkthrough — connecting to a J-Link probe, flashing firmware, loading ELF and SVD for symbol-aware debugging, RTT logging, and breakpoints.

Why this exists

If you've ever typed J-Link Commander commands by hand, copy-pasted memory addresses between a datasheet and a terminal, re-flashed the same firmware 20 times during a debug session, and juggled multiple tool windows — this is for you.

You have a microcontroller on a debug probe. You want an AI agent to interact with it — connect, flash firmware, read/write memory, reset, halt, resume. This server makes that possible.

It gives any MCP-compatible agent a full set of debug probe tools. The agent calls these tools, gets structured JSON back, and reasons about what to do next — without you manually driving JLinkExe for every operation.

What agents can do with it:

  • 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

Who is this for?

  • Embedded engineers — faster iteration: flash, debug, inspect memory conversationally
  • Hobbyists and makers — interact with microcontrollers without learning JLinkExe command syntax
  • QA and test engineers — automated flash-and-test sequences across multiple boards
  • Researchers — systematic exploration of embedded systems, register inspection

Quickstart (Claude Code)

pip install dbgprobe-mcp-server

# Register the MCP server with Claude Code
claude mcp add dbgprobe -- dbgprobe_mcp

# Or with explicit J-Link path
claude mcp add dbgprobe \
  -e DBGPROBE_JLINK_PATH=/Applications/SEGGER/JLink/JLinkExe \
  -- dbgprobe_mcp

Then in Claude Code, try:

"List attached debug probes, connect to the J-Link, and read 16 bytes from address 0x20000000."

Supported backends

The server is backend-agnostic — tool names (dbgprobe.*) stay the same regardless of which probe you use.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Dbgprobe: common questions

Is Dbgprobe MCP server safe?
Mostly: it is graded B (75/100). Read the Dbgprobe safety report
How do I install Dbgprobe?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Dbgprobe need an API key?
No secret keys are declared. It reads 9 settings from the environment.
Is Dbgprobe maintained?
The last commit was 198 days ago (2026-03-14). The latest release is v0.1.4.

More from es617 →