Ext Ops Panel
Open dashboard
Comparison

io.github.daedalus/mcp-gdbserver vs mcu-debug-mcp

io.github.daedalus/mcp-gdbserver is an MCP server published by daedalus. Marketplaces we read that list it: 1 (Official MCP Registry). mcu-debug-mcp is an MCP server published by stillsurge. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.daedalus/mcp-gdbservermcu-debug-mcp
Official MCP Registry Listed
Version: 0.1.1
Downloads/month (PyPI): 73
Downloads/week (PyPI): 23
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.daedalus/mcp-gdbserver vs mcu-debug-mcp
Factio.github.daedalus/mcp-gdbservermcu-debug-mcp
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp-gdbserver)On your machine (mcu-debug-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/daedalus/mcp-gdbservergithub.com/stillsurge/mcu-debug-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-23

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.daedalus/mcp-gdbserver

In its own words, on Official MCP Registry:

MCP server for remote debugging with gdbserver

mcu-debug-mcp

In its own words, on Official MCP Registry:

Embedded debug MCP: serial, flash verify, fault decode, 45-pattern log analyzer, driver library

How to run each

io.github.daedalus/mcp-gdbserver As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio mcp-gdbserver -- uvx mcp-gdbserver

mcu-debug-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio mcu-debug-mcp -- uvx mcu-debug-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of io.github.daedalus/mcp-gdbserver publish no settings it asks for, so we do not compare settings.

What it can do: io.github.daedalus/mcp-gdbserver · What it can do: mcu-debug-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built