Skip to main content
Glama
cunjun

McuBuddy

by cunjun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to McuBuddy

No user-submitted related servers found.

    Related Servers

    • dbgprobe-mcp-server

      es617
      A
      license
      A
      quality
      C
      maintenance
      Stateful MCP server for driving debug probes (J-Link) to flash, debug, and inspect embedded targets. Enables AI agents to perform flash, memory, breakpoint, and ELF/SVD-aware operations conversationally.
      41
      10
      MIT

    • Chiplab

      veecle
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for simulating firmware on virtual microcontroller instances, allowing AI agents to upload, run, and read UART output from supported boards such as STM32 and Nordic.
      16
      MIT

    • mcp-stm32cubeide-server

      Helistana
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that lets AI coding agents drive the full STM32 development loop—code generation, build, flash, debug, serial monitoring, and fault diagnosis—end to end via CubeIDE, CubeMX, CubeProgrammer, OpenOCD, and GDB.
      MIT

    • JLink MCP Server

      cyj0920
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that provides comprehensive debugging capabilities for J-Link debuggers, enabling memory, flash, register, and RTT operations through AI assistants.
      33
      MIT

    • DebugForge

      YangPan2020
      A
      license
      A
      quality
      B
      maintenance
      MCP server bridging Lauterbach TRACE32 debuggers to AI agents for autonomous debugging, providing 47 tools for execution control, breakpoints, memory, registers, variables, and symbol inspection.
      100
      8
      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

    C2.2/5.0

    Scored across 19 tools

    Disambiguation2/5

    Several tools have unclear or overlapping boundaries: configure_probe, probe_connect, and first_contact all relate to probe/debug session startup, while disconnect_all and finish_debug_session both end sessions. match_chip_name and get_target_info also overlap in alias resolution, and some tools have no description at all, making selection risky.

    Naming Consistency3/5

    Most tools follow a verb_noun pattern (list_, configure_, get_), but several break it: elf_load, svd_load, and pack_diagnose are noun_verb, and doctor and first_contact are one-off non-pattern names. Overall readable but noticeably inconsistent.

    Tool Count3/5

    Nineteen tools is on the heavy side for an MCU debug server, and some tools could be consolidated, especially around probe connection and session teardown. Still, the count is not extreme and many tools serve distinct preflight, validation, and configuration purposes.

    Completeness2/5

    The tool surface covers setup, probe detection, configuration, ELF/SVD loading, and a few validation/read-only checks, but core MCU debugging operations are missing: no read/write memory, no register access, no step/continue, no breakpoints, and no flash programming. This is a significant gap for a debug-oriented server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources