debug-dap-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG_DAP_MCP_LOG | No | Set the log level. Overrides the default log level. The CLI option --log-level takes precedence if provided. Possible values: debug, info, warn, error. | info |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| debugB | DAP (Debug Adapter Protocol) control surface. Pass one of 31 |
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 1 tool
There is only one tool, so no ambiguity exists between tools. The 31 DAP actions are internal parameters, not separate tools.
The single tool name `debug` is concise and matches the server's purpose. With only one tool, there is no conflicting naming pattern.
The entire DAP protocol is packed into one mult-i purpose dispatch tool, which feels too few for the apparent scope. A single optool acts as a god-parameter surface rather than a discoverable set.
The 31 actions likely cover the core DAP request lifecycle (launch, attach, breakpoints, stepping, evaluation, etc.), enabling complete debugging workflows. As a single control surface, there are no obvious dead ends.