debugpy-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| debugpy_list_containersD | – |
| debugpy_autodiscover_targetD | – |
| debugpy_statusD | – |
| debugpy_attachD | – |
| debugpy_contextD | – |
| debugpy_logsD | – |
| debugpy_debugpy_logsD | – |
| debugpy_breakpoint_planD | – |
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
The tools have distinct names, but some overlap exists in functionality, such as debugpy_logs and debugpy_debugpy_logs, which could cause confusion. However, most tools like debugpy_attach and debugpy_breakpoint_plan target different aspects of debugging, helping to differentiate them.
All tool names follow a consistent pattern of prefixing with 'debugpy_' and using snake_case throughout, such as debugpy_attach and debugpy_breakpoint_plan. There are no deviations in naming conventions, making the set predictable and readable.
With 8 tools, this server is well-scoped for a debugging domain, providing a focused set without being overwhelming. Each tool appears to serve a specific purpose in debugging workflows, such as attaching, logging, and status checking, which is appropriate for the scope.
The tools cover key debugging operations like attaching, logging, and status, but there are notable gaps, such as missing tools for stepping through code, setting breakpoints dynamically, or handling variables. This could limit agents in performing comprehensive debugging tasks.