J-Link MCP Server

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

Packages and local setup

The published npm package is jlink-mcp, version 0.6.0. Its declared MCP transport is stdio.

The package declares 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..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.6.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related other integrations MCP servers for tools that cover the same kind of work.