AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Embedded Debugger

skill-adancurusul-embedded-debugger-mcp-embedded-debugger · by Adancurusul

Embedded hardware debugging workflow for probe-rs targets using embedded-debugger-mcp. Use when Codex or Claude Code needs to inspect debug probes, validate embedded debugger setup, start the MCP server, guide a user through ARM Cortex-M/RISC-V flashing/debugging/RTT workflows, or operate without installing an MCP client by using the CLI plus prompts.

↗ Repository
— No reviews yet
0 installs
31 views
0.0% view→install

Install

$ agentstack add skill-adancurusul-embedded-debugger-mcp-embedded-debugger

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-adancurusul-embedded-debugger-mcp-embedded-debugger)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Embedded Debugger? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Embedded Debugger

Use the local embedded-debugger-mcp binary as the source of truth. Prefer CLI checks first, then MCP tools when an MCP client is available.

Entry Decision

  1. If the user has an MCP client configured, start or verify the server:

embedded-debugger-mcp serve

  1. If the user wants no MCP install, use CLI-first mode:

embedded-debugger-mcp doctor, embedded-debugger-mcp probes list, and embedded-debugger-mcp skill print-prompt.

  1. If hardware access is required, confirm the probe and target are connected

before destructive actions such as flash erase or program.

CLI Workflow

Run these in order and report the exact outcome:

embedded-debugger-mcp doctor
embedded-debugger-mcp probes list
embedded-debugger-mcp config show

Use JSON for automation:

embedded-debugger-mcp doctor --json
embedded-debugger-mcp probes list --json

MCP Workflow

Use MCP tools for session-based operations:

  1. list_probes
  2. connect
  3. Read-only checks such as probe_info, get_status, and read_memory
  4. Mutating operations only after the user confirms target, file path, and risk:

write_memory, flash_erase, flash_program, run_firmware

  1. RTT operations after firmware is running: rtt_attach, rtt_channels,

rtt_read, rtt_write, rtt_detach

  1. disconnect

Safety Rules

  • Treat flash erase, flash program, memory write, reset, run, and RTT write as

mutating hardware operations.

  • Prefer read-only discovery before mutation.
  • Respect project configuration limits for file paths, file sizes, memory

ranges, and flash erase permissions.

  • Do not claim hardware success from command text alone; cite the command or MCP

tool result that produced the evidence.

Prompt Reference

For a reusable CLI+Skill prompt, read references/default-prompt.md.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Developer Tools