How to add Embedded Debugger MCP Server to Claude Desktop

Debug embedded systems (ARM Cortex-M, RISC-V) from AI assistants via probe-rs. Paste the config into ~/Library/Application Support/Claude/claude_desktop_config.json and restart Claude Desktop.

Last updated June 14, 2026 · 113★ · stdio · no auth

Claude Desktop config for Embedded Debugger MCP Server

git clone https://github.com/adancurusul/embedded-debugger-mcp.git && cd embedded-debugger-mcp && cargo build --release

{
  "mcpServers": {
    "embedded-debugger-mcp-server": {
      "command": "/path/to/debugger-mcp-rs/target/release/embedded-debugger-mcp",
      "args": [],
      "env": {
        "RUST_LOG": "info"
      }
    }
  }
}

Setup steps

1Open Claude Desktop → Settings → Developer → Edit Config (this opens ~/Library/Application Support/Claude/claude_desktop_config.json).
2Paste the Embedded Debugger MCP Server config below under the top-level "mcpServers" key.
3Fill in any placeholder secrets (API keys, paths) in the snippet.
4Save the file, then fully quit and reopen Claude Desktop.
5Open a chat and confirm Embedded Debugger MCP Server's tools appear under the 🔌 tools menu.

Before you start

Rust 1.70+ to build from source
A probe-rs compatible debug probe (ST-Link V2/V3, J-Link, or DAPLink) with drivers installed
A supported target board (e.g. STM32 microcontroller)
USB connection to the probe and target board

What Embedded Debugger MCP Server can do in Claude Desktop

list_probes

Discover available debug probes on the system.

connect

Connect to a probe and target chip.

probe_info

Get detailed session information.

read_memory

Read flash/RAM with multiple data formats.

write_memory

Write to target memory.

halt

Stop target execution.

run

Resume target execution.

reset

Perform a hardware or software reset.

Security

Runs as a local stdio process and controls real debug hardware (flash erase/program, memory write, target reset). Only connect it to probes and target boards you intend to expose to the AI assistant.

Embedded Debugger MCP Server + Claude Desktop FAQ

Where is the Claude Desktop config file?

Claude Desktop reads MCP servers from ~/Library/Application Support/Claude/claude_desktop_config.json. Paste the Embedded Debugger MCP Server config there under the "mcpServers" key and restart the client.

Is Embedded Debugger MCP Server safe to use with Claude Desktop?

Runs as a local stdio process and controls real debug hardware (flash erase/program, memory write, target reset). Only connect it to probes and target boards you intend to expose to the AI assistant.

Which debug probes are supported?

J-Link (all variants), ST-Link V2/V3, ARM DAPLink-compatible probes, Black Magic Probe, and FTDI-based debug probes.

Which target architectures work?

ARM Cortex-M (M0, M0+, M3, M4, M7, M23, M33) and various RISC-V cores, with basic support for ARM Cortex-A.

Is there a prebuilt package?

No. The README documents building from source with cargo build --release; there is no npm or other registry package listed.

View repo Full Embedded Debugger MCP Server page