Skip to main content
Glama
MisakaMikoto128

J-Link RTT Viewer MCP

by MisakaMikoto128
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to J-Link RTT Viewer 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
      6
      MIT

    • jlink-mcp

      Klievan
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to debug embedded devices via SEGGER J-Link probes, including reading memory, flashing firmware, streaming RTT logs, and diagnosing crashes.
      47
      111 npm
      32
      MIT

    • stmctl-mcp

      Sathvik-smarttrak
      F
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to flash firmware, program memory, modify option bytes, erase chips, reset boards, and capture SWO printf traces for STM32 microcontrollers via STM32CubeCLT.
      12
      -

    • 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

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

    A3.7/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct operation (connect, disconnect, flash, memory read/write, RTT read/write, logging, reset, device info) with no overlapping purposes.

    Naming Consistency5/5

    All tools use consistent verb_noun snake_case naming (e.g., read_memory, write_rtt) with no deviations or mixed conventions.

    Tool Count5/5

    12 tools is well-scoped for a J-Link/RTT debugger, covering essential operations without being excessive or minimal.

    Completeness4/5

    Core operations (connect, flash, memory R/W, RTT R/W, logging, reset) are covered, but minor gaps like erase or verify exist.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources