J-Link MCP
Debug embedded firmware on real hardware: J-Link probes, Cortex-M faults, RTT logs, GDB.
Open the source (opens github.com) https://github.com/klievan/jlink-mcp
Before you use it
- Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
What it is
MCP servers from io.github.Klievan.
The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.
How to get it
npm package (stdio)
jlink-mcp@0.8.0
From the server's entry in the official MCP Registry
Settings it asks for
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
-
STM32 GDB Debugger
MCP serversDebug STM32 firmware on real hardware via GDB + OpenOCD/ST-Link/J-Link with decoded results.
stm32-gdb-mcp@0.15.1 -
GitHub MCP server
MCP serversGitHub's official MCP server. It lets an agent read and work with repositories, issues and pull requests.
https://api.githubcopilot.com/mcp/ -
Apify MCP server
MCP serversLets an agent run Apify's ready-made scrapers to pull data from websites, search engines, maps and social platforms.
-
Official MCP Registry
MCP serversThe MCP project's own registry of public MCP servers, so you can look for a connector before building one.
-
MCP reference servers
MCP serversSmall example servers from the MCP project (filesystem, git, fetch, memory and more) that show how MCP works.
-
Connect MCP servers to Claude Code
MCP serversAnthropic's guide to adding MCP servers to Claude Code, with examples of local and remote servers.