J-Link MCP Server

What the code does

We read the source, 21 h ago · rules 3dff92dd89df

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 this.config.installDir ? path.join(this.config.installDir, exe) : exe;

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

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 -- npx -y jlink-mcp

{
  "mcpServers": {
    "jlink-mcp": {
      "args": [
        "-y",
        "jlink-mcp"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.jlink-mcp]
command = "npx"
args = ["-y", "jlink-mcp"]

{
  "mcpServers": {
    "jlink-mcp": {
      "args": [
        "-y",
        "jlink-mcp"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "jlink-mcp": {
      "args": [
        "-y",
        "jlink-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: JLINK_DEVICE (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.). The author declared them in the registry entry; get the values from the project itself.