J-Link MCP vs STM32 GDB Debugger
J-Link MCP is an MCP server published by Klievan. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). STM32 GDB Debugger is an MCP server published by Zeraissh. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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
| Marketplace |  J-Link MCP |  STM32 GDB Debugger |
|---|---|---|
| Official MCP Registry | Listed Version: 0.8.0 Downloads/month (npm): 683 Downloads/week (npm): 218 Forks (GitHub): 6 Stars (GitHub): 43 Not marked · First seen |
Listed Version: 0.15.1 Downloads/month (PyPI): 52 Downloads/week (PyPI): 30 Forks (GitHub): 0 Stars (GitHub): 3 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
| Fact | J-Link MCP | STM32 GDB Debugger |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 43 (better) | 3 (worse) |
| Forks (GitHub) (differs) | 6 (better) | 0 (worse) |
| Last release (differs) | 2026-10-26 | Not published |
| Where it runs (differs) | On your machine (jlink-mcp) | On your machine (stm32-gdb-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 0 | 1, secrets among them: 0 |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/klievan/jlink-mcp | github.com/zeraissh/stm32-gdb-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-19 |
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
J-Link MCP
Debug embedded firmware on real hardware: J-Link probes, Cortex-M faults, RTT logs, GDB.
STM32 GDB Debugger
Debug STM32 firmware on real hardware via GDB + OpenOCD/ST-Link/J-Link with decoded results.
How to run each
J-Link MCP As a local MCP server: npm package
claude mcp add --env "JLINK_DEVICE=<YOUR_JLINK_DEVICE>" --transport stdio jlink-mcp -- npx -y jlink-mcpRequires: JLINK_DEVICE
STM32 GDB Debugger As a local MCP server: PyPI package
claude mcp add --transport stdio stm32-gdb-mcp -- uvx stm32-gdb-mcpCommands 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
Only J-Link MCP asks for
JLINK_DEVICEJLINK_RTT_ADDRJLINK_SERIALSVD_PATH
Only STM32 GDB Debugger asks for
STM32_GDB_MCP_COMPACT
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: J-Link MCP · What it can do: STM32 GDB Debugger · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.