MCP Tools DirectoryAbout this integration
Debug embedded firmware on real hardware: J-Link probes, Cortex-M faults, RTT logs, GDB.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- unknown
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.6.0
- Package
- jlink-mcp
- Last compatibility test
- Not independently tested
Connect your agent
jlink-mcpPublisher documentation and the package manifest were reviewed only; the package, probe software, hardware, firmware writes, and destructive debug tools were not executed or independently security-audited. The runtime requires local probe tooling and hardware. The README does not define a credential model for all vendor tooling, so authentication and setup remain unknown.
Capabilities: Inspect registers, memory, peripherals, and device state, Flash, erase, halt, reset, step, and resume embedded targets, Run GDB and RTT debugging workflows, Diagnose Cortex-M crashes, Operate J-Link, OpenOCD, or Black Magic Probe backends
Connected profiles
Additional details
io.github.Klievan/jlink-mcp
Source ↗ · Checked 2026-09-170.6.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17JLINK_DEVICE
Source ↗ · Checked 2026-09-17jlink-mcp
Source ↗ · Checked 2026-09-190.7.0
Source ↗ · Checked 2026-09-19The publisher documents direct npx startup of a standalone MCP process and identifies its transport as JSON-RPC over stdio.
Source ↗ · Checked 2026-09-19The captured prerequisites require locally installed probe software and connected hardware but do not establish a credential or license-authentication flow; authentication remains unknown.
Source ↗ · Checked 2026-09-19The MCP client connects over stdio to a local process, which in turn drives local probe software and a USB-connected target or configured local backend.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19