Back to Browse

Jlink MCP Server

Developer ToolsModerate5.3MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

5.3
Moderate5.3Moderate Risk

jlink-mcp is a local stdio MCP server for driving SEGGER J-Link, OpenOCD, and Black Magic probes for embedded debugging, and its permissions match that purpose. The main concerns are the raw probe_command tool, which lets the model run arbitrary probe commands, and the process spawning and termination paths, which are only partly visible in the truncated code. No exfiltration, hardcoded secrets, or malicious patterns were found in the provided files. Supply chain analysis found 8 known vulnerabilities in dependencies (0 critical, 5 high severity). Package verification found 1 issue.

5 files analyzed · 14 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

process_spawn

Check that this permission is expected for this type of plugin.

Shell Command Execution

Runs commands on your machine. Be cautious — only use if you trust this plugin.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

File System Write

Writes or modifies files on your machine. Check that this is expected for the tool.

env_vars

Check that this permission is expected for this type of plugin.

TCP Network Access

Opens direct network connections, common for database or messaging tools.

hardware_access

Check that this permission is expected for this type of plugin.

process_kill

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Target device name, exactly as J-Link spells it (e.g. nRF52840_XXAA, STM32F407VG). Use the search_devices tool to find it.Optional

Environment variable: JLINK_DEVICE

Serial number of a specific probe, when more than one is attached.Optional

Environment variable: JLINK_SERIAL

CMSIS-SVD file for the target. Without it, peripheral reads are undecoded hex.Optional

Environment variable: SVD_PATH

Address of the firmware's _SEGGER_RTT symbol. Lets RTT survive a reset or flash.Optional

Environment variable: JLINK_RTT_ADDR

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-klievan-jlink-mcp": {
      "env": {
        "SVD_PATH": "your-svd-path-here",
        "JLINK_DEVICE": "your-jlink-device-here",
        "JLINK_SERIAL": "your-jlink-serial-here",
        "JLINK_RTT_ADDR": "your-jlink-rtt-addr-here"
      },
      "args": [
        "-y",
        "jlink-mcp"
      ],
      "command": "npx"
    }
  }
}

Reviews

No reviews yet

Be the first to review this server!