MCP server for SEGGER J-Link debug probes — LLM-driven embedded debugging with RTT, GDB server, and Trice/Pigweed support
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
list_devicesScan for connected PROBES — the debuggers plugged into this machine, not target chips. Despite the name it does not list target devices; use search_devices for those. Shows probe serial numbers and whether one is reachable.Scan for connected PROBES — the debuggers plugged into this machine, not target chips. Despite the name it does not list target devices; use search_devices for those. Shows probe serial numbers and whether one is reachable.
No input schema was published for this tool.
check_setupCheck that everything needed to debug is in place: the probe software, a connected probe, a targetCheck that everything needed to debug is in place: the probe software, a connected probe, a target
No input schema was published for this tool.
set_svd_pathPoint the server at a CMSIS-SVD file for the target at runtime, so peripheral reads come backPoint the server at a CMSIS-SVD file for the target at runtime, so peripheral reads come back
No input schema was published for this tool.
set_rtt_addressTell the server where the firmware's RTT control block is (its _SEGGER_RTT symbol), at runtime.Tell the server where the firmware's RTT control block is (its _SEGGER_RTT symbol), at runtime.
No input schema was published for this tool.
search_devicesSearch the device names this J-Link installation accepts, by part number, manufacturer, or core.Search the device names this J-Link installation accepts, by part number, manufacturer, or core.
No input schema was published for this tool.
set_deviceSet the target device name at runtime. Required before any debugging commands will work.Set the target device name at runtime. Required before any debugging commands will work.
No input schema was published for this tool.
start_debug_sessionNo description publishedThis tool published no description. Forge does not invent one.
snapshotCapture complete device state: CPU registers (compact), fault status, recent RTT output, and stack dump.Capture complete device state: CPU registers (compact), fault status, recent RTT output, and stack dump.
No input schema was published for this tool.
diagnose_crashAuto-read and decode ARM Cortex-M fault registers (CFSR, HFSR, MMFAR, BFAR), exception stack frame, and recent errors.Auto-read and decode ARM Cortex-M fault registers (CFSR, HFSR, MMFAR, BFAR), exception stack frame, and recent errors.
No input schema was published for this tool.
device_infoNo description publishedThis tool published no description. Forge does not invent one.
haltHalt the target CPUHalt the target CPU
No input schema was published for this tool.
resumeResume the target CPUResume the target CPU
No input schema was published for this tool.
resetReset the target device. Halting leaves the core stopped at the reset vector,Reset the target device. Halting leaves the core stopped at the reset vector,
No input schema was published for this tool.
stepStep one CPU instructionStep one CPU instruction
No input schema was published for this tool.
read_memoryRead memory from the target. Returns clean hex dump.Read memory from the target. Returns clean hex dump.
No input schema was published for this tool.
write_memoryprivilegedWrite a 32-bit value to memoryWrite a 32-bit value to memory
No input schema was published for this tool.
read_registersRead all CPU registers (compact format, FP only if non-zero).Read all CPU registers (compact format, FP only if non-zero).
No input schema was published for this tool.
read_registerRead a specific CPU register by nameRead a specific CPU register by name
No input schema was published for this tool.
flashFlash firmware to the target deviceFlash firmware to the target device
No input schema was published for this tool.
eraseErase target flash memoryErase target flash memory
No input schema was published for this tool.
list_peripheralsList the target's peripherals and base addresses, from its CMSIS-SVD description. Requires an SVD file to be configured.List the target's peripherals and base addresses, from its CMSIS-SVD description. Requires an SVD file to be configured.
No input schema was published for this tool.
read_peripheralRead every register of a peripheral from the target and decode each one's bit fields by name. This is read_memory plus the meaning of what was read.Read every register of a peripheral from the target and decode each one's bit fields by name. This is read_memory plus the meaning of what was read.
No input schema was published for this tool.
decode_registerDecode a value into named bit fields using the target's SVD. Reads from the device unless a value is supplied — useful for interpreting a number you already have.Decode a value into named bit fields using the target's SVD. Reads from the device unless a value is supplied — useful for interpreting a number you already have.
No input schema was published for this tool.
set_breakpointSet a hardware breakpointSet a hardware breakpoint
No input schema was published for this tool.
clear_breakpointsClear all breakpoints, including any left armed in the debug hardware by an earlier sessionClear all breakpoints, including any left armed in the debug hardware by an earlier session
No input schema was published for this tool.
gdb_server_startNo description publishedThis tool published no description. Forge does not invent one.
gdb_server_stopNo description publishedThis tool published no description. Forge does not invent one.
gdb_server_statusGet GDB server, RTT, and telnet proxy statusGet GDB server, RTT, and telnet proxy status
No input schema was published for this tool.
gdb_connectConnect a GDB client to the running GDB server. Enables source-level debugging: backtraces, variable inspection, conditional breakpoints, stepping by source line. Optionally load an ELF file for symbol info.Connect a GDB client to the running GDB server. Enables source-level debugging: backtraces, variable inspection, conditional breakpoints, stepping by source line. Optionally load an ELF file for symbol info.
No input schema was published for this tool.
gdb_commandprivilegedSend any GDB command and get the response. For execution commands (continue, step, next, finish, until), blocks until the target stops or times out. If the target doesn't stop, use gdb_wait to poll. Examples: 'bt' (backtrace), 'info threads', 'print myVar', 'break main', 'continue', 'next', 'step',…Send any GDB command and get the response. For execution commands (continue, step, next, finish, until), blocks until the target stops or times out. If the target doesn't stop, use gdb_wait to poll. Examples: 'bt' (backtrace), 'info threads', 'print myVar', 'break main', 'continue', 'next', 'step',…
No input schema was published for this tool.
gdb_waitPoll for target stop after a continue/step that timed out. Returns the stop reason (breakpoint hit, signal, finished stepping, etc.) when the target halts.Poll for target stop after a continue/step that timed out. Returns the stop reason (breakpoint hit, signal, finished stepping, etc.) when the target halts.
No input schema was published for this tool.
gdb_loadLoad an ELF file into GDB. By default loads symbols only (for source-level debugging: backtraces with file:line, variable names). Set flash=true to also program it onto the target.Load an ELF file into GDB. By default loads symbols only (for source-level debugging: backtraces with file:line, variable names). Set flash=true to also program it onto the target.
No input schema was published for this tool.
gdb_backtraceGet a stack backtrace. With debug symbols loaded, shows function names, file paths, and line numbers.Get a stack backtrace. With debug symbols loaded, shows function names, file paths, and line numbers.
No input schema was published for this tool.
gdb_disconnectDisconnect the GDB client (does not stop the GDB server)Disconnect the GDB client (does not stop the GDB server)
No input schema was published for this tool.
rtt_connectNo description publishedThis tool published no description. Forge does not invent one.
rtt_disconnectDisconnect from RTTDisconnect from RTT
No input schema was published for this tool.
rtt_readRead RTT log lines (clean, parsed Zephyr format). Non-destructive — reading does not consumeRead RTT log lines (clean, parsed Zephyr format). Non-destructive — reading does not consume
No input schema was published for this tool.
rtt_searchSearch/filter RTT logs by level, module, or regexSearch/filter RTT logs by level, module, or regex
No input schema was published for this tool.
rtt_sendSend data to device via RTT down-channelSend data to device via RTT down-channel
No input schema was published for this tool.
rtt_statusRead SEGGER's RTT control block on the target: is it initialised, how much has the firmwareRead SEGGER's RTT control block on the target: is it initialised, how much has the firmware
No input schema was published for this tool.
35 of 40 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server for SEGGER J-Link debug probes — LLM-driven embedded debugging with RTT, GDB server, and Trice/Pigweed support
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+42 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.