
Mcp Gdbserver
io.github.daedalusPublished by GitHub account daedalusv0.1.1Updated Oct 24, 2026
MCP server for remote debugging with gdbserver
Overview
A local MCP server that lets an assistant drive gdbserver remote debugging sessions: start or attach to processes, set breakpoints, step, and inspect memory and
- What you can do
- Start, attach to, list and stop gdbserver debugging sessions, including multi-process mode and attaching to running processes. Set and delete breakpoints at chosen locations. Control execution by continuing, stepping into or over instructions, and interrupting. Inspect state: call stack frames, local variables, threads, thread switching, CPU registers, memory contents, expression evaluation, and loading symbol files.
- When to use it
- Useful when debugging native programs with gdbserver and you want an assistant to drive the session: launching a target, setting breakpoints, stepping through code, and reading stack, variables, registers or memory without switching to a GDB prompt.
- Requirements
- Runs as a local process on the user's machine, installed from PyPI (pip install mcp-gdbserver) and configured as a stdio MCP server. Desktop only; no web execution. gdbserver and the target program must be available locally, and a port is chosen when starting a session. No authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open Mcp Gdbserver in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
mcp-gdbserver
MCP server for remote debugging with gdbserver - provides full debugging capabilities including process management, breakpoint control, stepping, memory inspection, and more.
[PyPI] [Python] [Coverage] [Ruff]
Install
Usage
CLI
Tools
The MCP server provides 19 debugging tools organized into 4 categories:
Process Management
gdbserver_start- Start gdbserver to debug a program remotelygdbserver_start_multi- Start gdbserver in multi-process modegdbserver_attach- Attach to a running processgdbserver_list_sessions- List all active sessionsgdbserver_stop- Stop a debugging session
Breakpoint Control
gdbserver_set_breakpoint- Set a breakpoint at a locationgdbserver_delete_breakpoint- Delete a breakpoint
Execution Control
gdbserver_continue- Continue executiongdbserver_step- Step one instruction (into functions)gdbserver_next- Execute one instruction (over functions)gdbserver_interrupt- Interrupt execution
Inspection
gdbserver_stack_frames- Get call stack framesgdbserver_local_variables- Get local variablesgdbserver_list_threads- List all threadsgdbserver_select_thread- Switch to a threadgdbserver_read_register- Read CPU registersgdbserver_read_memory- Read memory contentsgdbserver_evaluate- Evaluate an expressiongdbserver_load_symbols- Load symbol file
MCP Configuration
Add to your MCP config:
Development
mcp-name: io.github.daedalus/mcp-gdbserver
Source: README.md at commit 2aebe8c
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts