Skip to main content
Glama

Related Servers

Alternatives to STM32 GDB MCP Server

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
    • 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
      -
    • 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
      A
      quality
      C
      maintenance
      Enables AI tools to perform full-featured embedded microcontroller debugging via pyOCD and CMSIS-DAP probes, including probe management, flashing, breakpoints, register/memory access, fault analysis, and RTT communication.
      58
      1
      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
      7
      MIT
    • 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

    TDQS

    A3.5/5.0

    Scored across 86 tools

    Disambiguation3/5

    Many tools overlap in the run/stop/context-capture space (run_and_wait, wait_for_stop, continue_execution, run_for_duration, run_to_line, capture_state) and multiple meta-call tools (call, call_read, batch, tool_help) create selection ambiguity. Descriptions are detailed enough to mostly disambiguate, but with 86 tools an agent can still easily misselect.

    Naming Consistency4/5

    Most names follow a predictable snake_case verb_noun pattern (start_debug_session, read_memory, flash_firmware, solve_clock_tree). A minority are single-noun mega-tools (hub, breakpoint, expressions, logging, frame, snapshot), which is a minor deviation but still readable and internally consistent within that subset.

    Tool Count2/5

    86 tools is far beyond the well-scoped 3-15 range and is too many even for this broad server. Although it spans debug, build, board design, acceptance loops, and USB hub control, the surface is unwieldy and likely to overwhelm clients and agents; consolidation into more action-parameter mega-tools is needed.

    Completeness5/5

    The tool surface covers the embedded debug lifecycle comprehensively: sessions, flashing, symbols, memory/registers, breakpoints, RTOS, SVD, fault/stack recovery, logging, profiling, coredump, acceptance loops, netlist-to-framework design, clock/timer solving, and hub power control. No obvious domain gap remains for the stated STM32 GDB/debug-and-build purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive