Enterprise DNAEnterprise DNA

MCP Servers

adancurusul/embedded-debugger-mcp

A Model Context Protocol server for embedded debugging with probe-rs - supports ARM Cortex-M, RISC-V debugging via J-Link, ST-Link, and more

Visit site ↗

Our verdict

Not reviewed yet

We have not reviewed adancurusul/embedded-debugger-mcp yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About adancurusul/embedded-debugger-mcp

A Model Context Protocol server that enables LLMs to perform embedded debugging via probe-rs. It supports ARM Cortex-M and RISC-V targets using J-Link, ST-Link, and other debug probes. The tool acts as an MCP endpoint, allowing AI agents to read/write memory, set breakpoints, and control execution.

Best for

Developers integrating LLMs into embedded debugging workflows

Use cases

  • Debug embedded firmware through natural language commands
  • Automate flash, reset, and register inspection with LLMs
  • Integrate probe-controlled testing into AI-assisted development pipelines

Notes

99 stars on GitHub. Last updated 2025-08-06. Licensed MIT.

Pros

  • Open source with 99 stars, community-backed
  • Supports multiple architectures (ARM Cortex-M, RISC-V) and common probes
  • Written in Rust for performance and reliability

Cons

  • Requires physical hardware and probe connected to a host
  • Limited to debug probes supported by probe-rs (not universal)
  • Setup requires Rust toolchain and knowledge of MCP configuration

Key facts

What we have checked

Days since the last commit
102
Checked GitHub
GitHub forks
33
Checked GitHub
GitHub stars
210
Checked GitHub
Open issues
2
Checked GitHub
Releases in the last 90 days
0
Checked GitHub

Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.

How to use

How to set it up

As the listing publishes it. We have not run this install.

Install

cargo build --release

Tools exposed

  • list_probes
  • connect
  • probe_info
  • halt
  • run
  • reset
  • step
  • get_status
  • disconnect
  • read_memory
  • write_memory
  • set_breakpoint
  • clear_breakpoint
  • diagnose_fault
  • unwind_exception
  • flash_erase
  • flash_program
  • flash_verify
  • run_firmware
  • rtt_attach

Clients the listing names (not checked here)

Claude Code, Codex

Example client config

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

Install

Add adancurusul/embedded-debugger-mcp to your client

Not verified yet

No install recipe yet. We write one for Claude Code, Claude Desktop, Cursor, VS Code, Codex and ChatGPT when the server is in the official MCP registry with a package or remote address we can use.

Until then, follow the project's own README, or the setup the listing publishes under How to set it up.

Works with

What adancurusul/embedded-debugger-mcp connects to

No confirmed connections yet. A product appears here when the server's registry name, repo, homepage or name ties it to that product, and a client appears when we have an install recipe for it.

Health and security

Is adancurusul/embedded-debugger-mcp looked after, and what do its setup files show

Health score

29 out of 100

Does someone look after this repository? It does not say the code is good or safe. Worked out from GitHub signals checked . How it is worked out

PartPointsWhat we saw
Recent activity23.6 of 30Last push 102 days ago
Releases0 of 150 releases in 90 days
Issue repliesNot countedThe latest check has no issue response reading (fewer than 3 measured issues, or issues switched off)
Maintainer0 of 15Owned by a single user
Official source0 of 20Community server

Security check static checks

100 out of 100

Reads what is published about the server: package advisories, licence, secrets in the documented setup and tool permissions. Nothing is installed or run, so this is not a security assessment. Checked by edna-static-v1. What it checks

Licence: MIT

  • Note No published npm or PyPI package of this repository was found, so package advisories were not checked.
  • Note The lab has not recorded this server's tool list yet, so tool permissions were not checked.
Tool permissions (1)
  • RUST_LOG, environment variable it asks for

Sources

Where this comes from

  • GitHubRegistry

    Checked · Days since the last commit, GitHub forks, GitHub stars, Open issues, Releases in the last 90 days

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.

← Back to MCP ServersSubmit your own entry →