io.github.daedalus/mcp-gdbserver

Official registry Developer tools

MCP server for remote debugging with gdbserver

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

PYPI package mcp-gdbserver
Claude Code
claude mcp add mcp-gdbserver -- uvx mcp-gdbserver==0.1.1
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "mcp-gdbserver": {
            "command": "uvx",
            "args": [
                "mcp-gdbserver==0.1.1"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. mcp-gdbserver
  2. Install
  3. Usage
  4. CLI
  5. Tools
  6. MCP Configuration
  7. Development

mcp-gdbserver

MCP server for remote debugging with gdbserver - provides full debugging capabilities including process management, breakpoint control, stepping, memory inspection, and more.

Install

pip install mcp-gdbserver

Usage

from mcp_gdbserver import GdbDebugger

# Create debugger instance
debugger = GdbDebugger()

# Start gdbserver to debug a program
session = debugger.start_gdbserver(port=2345, program="/bin/myapp", args=["--debug"])

# Get session info
sessions = debugger.list_sessions()

# Stop session
debugger.stop_session("session_1")

CLI

mcp-gdbserver --help

Tools

The MCP server provides 19 debugging tools organized into 4 categories:

Process Management
  • gdbserver_start - Start gdbserver to debug a program remotely
  • gdbserver_start_multi - Start gdbserver in multi-process mode
  • gdbserver_attach - Attach to a running process
  • gdbserver_list_sessions - List all active sessions
  • gdbserver_stop - Stop a debugging session
Breakpoint Control
  • gdbserver_set_breakpoint - Set a breakpoint at a location
  • gdbserver_delete_breakpoint - Delete a breakpoint
Execution Control
  • gdbserver_continue - Continue execution
  • gdbserver_step - Step one instruction (into functions)
  • gdbserver_next - Execute one instruction (over functions)
  • gdbserver_interrupt - Interrupt execution
Inspection
  • gdbserver_stack_frames - Get call stack frames
  • gdbserver_local_variables - Get local variables
  • gdbserver_list_threads - List all threads
  • gdbserver_select_thread - Switch to a thread
  • gdbserver_read_register - Read CPU registers
  • gdbserver_read_memory - Read memory contents
  • gdbserver_evaluate - Evaluate an expression
  • gdbserver_load_symbols - Load symbol file

MCP Configuration

Add to your MCP config:

{
  "mcpServers": {
    "mcp-gdbserver": {
      "command": "mcp-gdbserver",
      "env": {}
    }
  }
}

Development

git clone https://github.com/daedalus/mcp-gdbserver.git
cd mcp-gdbserver
pip install -e ".[test]"

# run tests
pytest

# format
ruff format src/ tests/

# lint
ruff check src/ tests/

# type check
mypy src/

mcp-name: io.github.daedalus/mcp-gdbserver

Frequently asked questions

What is io.github.daedalus/mcp-gdbserver?

MCP server for remote debugging with gdbserver

How do I install io.github.daedalus/mcp-gdbserver?

It runs on your machine. In Claude Code: claude mcp add mcp-gdbserver -- uvx mcp-gdbserver==0.1.1. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.daedalus/mcp-gdbserver need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.daedalus/mcp-gdbserver open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.daedalus/mcp-gdbserver?

It is published by daedalus. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.