Home › Other › klievan/jlink-mcp
klievan/jlink-mcp
Debug embedded firmware on real hardware: J-Link probes, Cortex-M faults, RTT logs, GDB.
Connect
Review any command before running it. Package names and URLs come from the server's own registry entry.
Package (npm 0.8.0)
npx -y [email protected]
Or add to your MCP client config:
{
"mcpServers": {
"jlink-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"JLINK_DEVICE": "<YOUR_VALUE>",
"JLINK_SERIAL": "<YOUR_VALUE>",
"SVD_PATH": "<YOUR_VALUE>",
"JLINK_RTT_ADDR": "<YOUR_VALUE>"
}
}
}
}
JLINK_DEVICErequired — Target device name, exactly as J-Link spells it (e.g. nRF52840_XXAA, STM32F407VG). Use the search_devices tool to find it.JLINK_SERIAL— Serial number of a specific probe, when more than one is attached.SVD_PATH— CMSIS-SVD file for the target. Without it, peripheral reads are undecoded hex.JLINK_RTT_ADDR— Address of the firmware's _SEGGER_RTT symbol. Lets RTT survive a reset or flash.
Related servers
REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
browser-use
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
paperclip
Trending hip-hop artist momentum scores across four cultural dimensions.
World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 102 tools.
Front-End Checklist
Review frontend code and live pages against 386 quality-gated web development rules.
tldraw
Draw and visually collaborate with your agents on tldraw's canvas.
Data from the Official MCP Registry