MCP to use the python debugger, inspired by debug-gym
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-pdb","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# MCP-PDB: Python Debugger Interface for Claude/LLMs   MCP-PDB provides tools for using Python's debugger (pdb) with Claude and other LLMs through the Model Context Protocol (MCP). This was inspired by [debug-gym](https://microsoft.github.io/debug-gym/) by Microsoft, which showed gains in various coding benchmarks by providing a coding agent access to a python debugger. ## ⚠️ Security Warning This tool executes Python code through the debugger. Use in trusted environments only. ## Installation Works best with [uv](https://docs.astral.sh/uv/getting-started/features/) ### Claude Code ```bash # Install the MCP server claude mcp add mcp-pdb -- uv run --with mcp-pdb mcp-pdb # Alternative: Install with specific Python version claude mcp add mcp-pdb -- uv run --python 3.13 --with mcp-pdb mcp-pdb # Note: The -- separator is required for Claude Code CLI ``` ### Windsurf ```json { "mcpServers": { "mcp-pdb": { "command": "uv", "args": [ "run", "--with", "mcp-pdb", "mcp-pdb" ] } } } ``` ## Available Tools | Tool | Description | |------|-------------| | `start_debug(file_path, use_pytest, args)` | Start a local debugging session for a Python file | | `connect_remote_debug(host, port, timeout)` | Connect to a remote PDB session over TCP | | `send_pdb_command(command)` | Send a command to the running PDB instance (local or remote) | | `set_breakpoint(file_path, line_number)` | Set a breakpoint at a specific line | | `clear_breakpoint(file_path, line_number)` | Clear a breakpoint at a specific line | | `list_breakpoints()` | List all current breakpoints | | `restart_debug()` | Restart/reconnect the current debugging session | | `examine_variable(variable_name)` | Get detailed information about a variable | | `get_debug_status()` | Show the current state of the debugging session | | `end_…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.