Debug-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYTHONUNBUFFERED | No | Ensures Python output is sent straight to terminal without being buffered | 1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sessions_createB | Create a new debug session for a Python script |
| sessions_breakpointA | Run to a breakpoint and capture local variables |
| sessions_continueC | Continue execution to the next breakpoint |
| sessions_stateB | Get the current state of a debug session |
| sessions_endC | End a debug session and clean up resources |
| sessions_step_inB | Step into the next function call (requires active breakpoint) |
| sessions_step_overB | Step over the current line (requires active breakpoint) |
| sessions_step_outB | Step out of the current function (requires active breakpoint) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose within the debug session lifecycle: create, end, state, breakpoint, continue, and three distinct step types. The descriptions specify unique actions like 'step into' vs 'step over', eliminating any ambiguity between tools.
All tools follow a perfect 'sessions_verb' pattern (e.g., sessions_create, sessions_step_over). This consistent naming convention makes the tool set predictable and easy to understand at a glance.
With 8 tools, this server provides a well-scoped set for debugging operations. It covers the essential debug session lifecycle (create, state, end) and core execution control (breakpoint, continue, step variations) without being overwhelming or sparse.
The tool set offers complete coverage for a debug session domain: creation, state monitoring, execution control (breakpoint, continue, step in/out/over), and cleanup. There are no obvious gaps; agents can fully manage debug sessions from start to finish.