J-Link MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 158 installs a week from npm. Last commit 26 Oct 2026.
Debug embedded firmware on real hardware: J-Link probes, Cortex-M faults, RTT logs, GDB.
What the code does
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
this.proc = spawn(this.gdbPath, args, {
return config.installDir ? path.join(config.installDir, exe) : exe;
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add jlink-mcp -e 'JLINK_DEVICE=<JLINK_DEVICE>' -- npx -y jlink-mcp{
"mcpServers": {
"jlink-mcp": {
"command": "npx",
"args": [
"-y",
"jlink-mcp"
],
"env": {
"JLINK_DEVICE": "<JLINK_DEVICE>"
}
}
}
}[mcp_servers.jlink-mcp]
command = "npx"
args = ["-y", "jlink-mcp"]
env = { JLINK_DEVICE = "<JLINK_DEVICE>" }{
"mcpServers": {
"jlink-mcp": {
"command": "npx",
"args": [
"-y",
"jlink-mcp"
],
"env": {
"JLINK_DEVICE": "<JLINK_DEVICE>"
}
}
}
}{
"servers": {
"jlink-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"jlink-mcp"
],
"env": {
"JLINK_DEVICE": "<JLINK_DEVICE>"
}
}
}
}Put your own value in place of
<JLINK_DEVICE> (Target device name, exactly as J-Link spells it (e.g. nRF52840_XXAA, STM32F407VG). Use the search_devices tool to find it).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
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).
Alternatives to J-Link MCP
same job, measured the same wayBuild, flash, monitor, and test ESP-IDF projects on real hardware.
Embedded debug MCP: serial, flash verify, fault decode, 45-pattern log analyzer, driver library
Read-only MCP server to inspect an Android device over ADB: hardware, packages, permissions, logs.
Read-only VMware incident correlation: timeline, spikes, root-cause routing. 2 MCP tools.
Safe Google Workspace admin for AI agents: read-only by default, confirm-gated deletes, audit log.
Read contacts, projects, documents and log entries, and run read-only queries in HERO Software.
Send a file to a user or agent as a share link with expiry, max opens, approval, revoke and logs.
Judge hardware timing/serial against a contract: pass/marginal/fail (WS2812, DShot, logs)
J-Link MCP — questions
Answers built from our own checks of this server.