Skip to main content
Glama
Sign In
J-Link RTT Viewer MCP

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

    • jlink-mcp

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

    • stmctl-mcp

      Sathvik-smarttrak
      A
      license
      A
      quality
      D
      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
      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
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    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.

    Resources