gdb-mcp vs io.github.TomasLucasUTN/godot-mcp-bridge
gdb-mcp is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑26.
gdb-mcp is a plugin bundle for AI coding tools published by BeaCox. No marketplace we read lists it any more. io.github.TomasLucasUTN/godot-mcp-bridge is an MCP server published by TomasLucasUTN. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-30. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.TomasLucasUTN/godot-mcp-bridge | |
|---|---|---|
| Community marketplace beacox/gdb-mcp | Removed on 2026-10-26 Version: 0.4.0 Forks (GitHub): 2 Stars (GitHub): 10 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.2.1 Downloads/month (npm): 909 Downloads/week (npm): 140 Forks (GitHub): 2 Stars (GitHub): 10 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.2.1 Downloads/month (npm): 909 Downloads/week (npm): 140 Forks (GitHub): 2 Stars (GitHub): 10 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 | gdb-mcpno longer listed · | io.github.TomasLucasUTN/godot-mcp-bridge |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) | 10 | 10 |
| Forks (GitHub) | 2 | 2 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (godot-mcp-bridge) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/beacox/gdb-mcp | github.com/tomaslucasutn/godot-mcp-bridge |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of gdb-mcp
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
mcp-gdbserver io.github.daedalus/mcp-gdbserver
MCP server for remote debugging with gdbserver
-
smolmux-gdb-mcp io.github.magnusmalm/smolmux-gdb-mcp
GDB/SWD MCP server over a smolmux broker: breakpoints, memory, Cortex-M fault decode, board probing.
-
Windows x64dbg/x32dbg debugging with guarded sessions, breakpoints, memory and runtime evidence.
-
Debug STM32 firmware on real hardware via GDB + OpenOCD/ST-Link/J-Link with decoded results.
-
Native runtime debugging via DAP-to-MCP for crashes, hangs, dumps, symbols, and forensics.
-
MCP server giving AI agents eyes on OpenImageDebugger buffers in live gdb/lldb sessions
What each says it does
gdb-mcp
Multi-session GDB and gdbserver debugging through MCP.
io.github.TomasLucasUTN/godot-mcp-bridge
MCP server for Godot game engine integration — control the Godot editor with AI
How to run each
gdb-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.TomasLucasUTN/godot-mcp-bridge As a local MCP server: npm package
claude mcp add --transport stdio godot-mcp-bridge -- npx -y godot-mcp-bridgeCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: gdb-mcp · What it can do: io.github.TomasLucasUTN/godot-mcp-bridge · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.