Skip to main content
Glama
Klievan

jlink-mcp

by Klievan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to jlink-mcp

No user-submitted related servers found.

    Related Servers

    • jlink-mcp

      xun123456
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants like Claude to directly debug microcontrollers via JLink, supporting breakpoints, single-step, memory/register access, variable inspection, RTT logging, and firmware flashing.
      25
      5
      MIT

    • MCP J-Link Server

      gghammer
      A
      license
      A
      quality
      D
      maintenance
      Enables AI to directly control SEGGER J-Link embedded debug probes via the Model Context Protocol for debugging and firmware management. Users can perform tasks like reading registers, analyzing memory, flashing firmware, and tracking RTT logs using natural language commands.
      21
      1
      MIT

    • J-Link RTT Viewer MCP

      MisakaMikoto128
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to interact with STM32 development boards via J-Link debugger using RTT communication, supporting connection, logging, memory operations, and firmware flashing through natural language.
      12
      1
      MIT
    • sbl-debugger by soundbytelabs

      sbl-debuggerofficial

      soundbytelabs
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to debug ARM Cortex-M targets via GDB and OpenOCD, supporting attach, breakpoints, stepping, register/memory inspection, and SVD peripheral decoding.
      MIT

    • pyocd-debug-mcp

      konbakuyomu
      A
      license
      A
      quality
      D
      maintenance
      Enables AI tools to perform full-featured embedded microcontroller debugging via pyOCD and CMSIS-DAP probes, including probe management, flashing, breakpoints, register/memory access, fault analysis, and RTT communication.
      58
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 47 tools

    Disambiguation4/5

    Most tools map cleanly to distinct actions (halt, resume, step, reset, read_memory, write_memory, flash), and descriptions explicitly separate list_devices from search_devices and rtt_status from rtt_read. Minor overlap exists between snapshot and diagnose_crash, and between device_info and read_registers, but the boundaries are generally discoverable.

    Naming Consistency4/5

    Tool names consistently use lowercase snake_case and mostly follow verb_noun or domain-prefixed patterns (read_memory, set_device, rtt_read, gdb_command, telnet_proxy_start). A few outliers like snapshot, device_info, and gdb_server_start bend the pattern, but the naming remains predictable overall.

    Tool Count2/5

    47 tools is well above the typical well-scoped range and even past the 16-25 'heavy' band, making operator selection harder. The set could be consolidated, especially the granular GDB server, telnet proxy, and session lifecycle tools.

    Completeness5/5

    The tool surface is extremely thorough for J-Link debugging: device setup, halt/resume/step, memory/flash, breakpoints, fault decoding, SVD peripherals, RTT, GDB server/client integration, telnet proxy, and raw probe commands are all covered. There are no obvious dead ends for typical debug workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources