Skip to main content
Glama
xun123456

jlink-mcp

by xun123456
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to jlink-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      71 npm
      30
      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

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

    • MCUDebugforAI

      SingleDemo
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to compile, debug, sample, and inspect MCU firmware through J-Link/pyOCD or a mock engine, including breakpoints, watchpoints, single-stepping, register access, and flash dump operations.
      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

    A4/5.0

    Scored across 25 tools

    Disambiguation5/5

    Each tool has a well-defined and unique purpose. For example, read_memory, read_registers, and read_variable target different data sources. Breakpoint operations are clearly separated into set, clear, list, and clear_all. There is no ambiguity between tools.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., read_memory, set_breakpoint, flash_firmware). No mixing of camelCase or other conventions. The naming is predictable and intuitive.

    Tool Count4/5

    With 25 tools, the server covers a comprehensive debug workflow. While slightly above the ideal 3-15 range, each tool is justified and necessary for a full-featured debug adapter. The count is reasonable given the domain.

    Completeness5/5

    The tool set covers all essential debugger operations: connection management, firmware flashing, ELF symbol loading, memory/register read/write, breakpoints, stepping, run/halt, RTT communication, and symbol queries. No obvious gaps exist for a JLink debug interface.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources