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
      7
      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
      D
      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

    • STM32 J-Link MCP

      jpdev2022
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to program, debug, and diagnose STM32H7S3 microcontrollers through SEGGER J-Link, with stateful debug sessions, memory/flash operations, GDB integration, RTT logging, and safety controls.
      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
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.3/5.0

    Scored across 48 tools

    Disambiguation3/5

    There is substantial overlap between direct probe controls, GDB client wrappers, and catch-all tools: halt/resume/step vs. gdb_command continue/step, device_info vs. read_registers, and snapshot/diagnose_crash/check_setup all touch related state. Descriptions explicitly warn about several pitfalls and distinguish some boundaries, but an agent still faces multiple valid-seeming paths for common debug operations.

    Naming Consistency4/5

    Most names are snake_case and many use consistent resource prefixes such as gdb_, rtt_, and telnet_proxy_. There are minor deviations: bare verbs like halt, resume, step, and snapshot mix with verb_noun tools, and device-related names like list_devices, search_devices, and device_info are not perfectly parallel.

    Tool Count2/5

    The 48-tool surface is far beyond the typical well-scoped range, even for a rich embedded-debug domain. Much of the count comes from layered APIs plus start/stop/status triples and many small configuration setters, which could be consolidated.

    Completeness4/5

    The server covers probe discovery/configuration, GDB server and client control, flashing/reset, memory and register access, breakpoints, SVD-based peripheral decoding, RTT, telnet proxy, and crash diagnostics. Minor gaps exist, such as clearing/listing individual breakpoints and varied memory write widths, but catch-all gdb_command and probe_command mitigate many dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources