Home › Other › J-Link MCP

J-Link MCP

Debug embedded firmware on real hardware: J-Link probes, Cortex-M faults, RTT logs, GDB.

TypeScript

★ 32 stars Last pushed 2026-09-15 License: MIT

View repository → Website →

Connect

Review any command before running it. Package names and URLs come from the server's own registry entry.

Package (npm 0.6.0)

npx -y jlink-mcp@0.6.0

Or add to your MCP client config:

{
  "mcpServers": {
    "jlink-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "jlink-mcp@0.6.0"
      ],
      "env": {
        "JLINK_DEVICE": "<YOUR_VALUE>",
        "JLINK_SERIAL": "<YOUR_VALUE>",
        "SVD_PATH": "<YOUR_VALUE>",
        "JLINK_RTT_ADDR": "<YOUR_VALUE>"
      }
    }
  }
}

JLINK_DEVICE required — 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.