Skip to main content
Glama

Related Servers

Alternatives to pyocd-debug-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • 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
    • 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
    • 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
    • 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
    • F
      license
      A
      quality
      D
      maintenance
      Enables AI agents to debug embedded systems by providing a comprehensive interface for GDB operations across multiple architectures like ARM and x86. It supports remote debugging via gdbserver or QEMU, allowing for detailed inspection of memory, registers, stack frames, and variables.
      31
      -

    TDQS

    A3.8/5.0

    Scored across 58 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose within its category (breakpoints, debug analysis, ELF, flash, memory, probes, project, RTT, session, SVD, target, watchpoints). Descriptions are detailed and unique, preventing confusion.

    Naming Consistency5/5

    All tool names follow a consistent pyocd_<category>_<action> pattern in snake_case, e.g., pyocd_breakpoint_set, pyocd_debug_backtrace. The convention is uniform across all 58 tools.

    Tool Count3/5

    The server has 58 tools, which is high for an MCP server. While the domain (embedded debugging) is broad and each tool serves a specific function, this count is on the heavy side and may be overwhelming, slightly exceeding the ideal range.

    Completeness5/5

    The tool surface covers the complete debugging workflow: breakpoints, watchpoints, flash programming, memory/register access, SVD peripherals, RTT, project config, and target control. No obvious gaps for typical debug operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues