mcp-dap
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
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| debug_launchA | Launch a program for debugging. Returns session_id for subsequent operations. For Rust: use adapter='rust' with either 'program' (pre-built binary) or 'cargo_args' (e.g., ['build', '--bin', 'myapp']) to build and debug. |
| debug_attachA | Attach to a running debug server or process. Returns session_id for subsequent operations. For Python: provide host/port. For Rust: provide pid or program name. |
| debug_disconnectA | Disconnect from a debug session and optionally terminate the debuggee. |
| debug_set_breakpointsA | Set breakpoints in a source file. Replaces all existing breakpoints in that file. |
| debug_clear_breakpointsA | Clear all breakpoints in a source file. |
| debug_continueA | Continue execution. Blocks until execution stops (breakpoint, exception, etc.). |
| debug_step_overA | Step over to the next line. Blocks until step completes. |
| debug_step_intoA | Step into function call. Blocks until step completes. |
| debug_step_outA | Step out of current function. Blocks until step completes. |
| debug_pauseC | Pause execution. |
| debug_get_threadsA | Get all threads in the debuggee. |
| debug_get_stack_traceC | Get the call stack for a thread. |
| debug_get_scopesB | Get variable scopes for a stack frame (locals, globals, etc.). |
| debug_get_variablesC | Get variables for a scope or expandable variable. |
| debug_evaluateC | Evaluate an expression in the debuggee context. |
| debug_get_pending_eventsB | Get pending debug events (stopped, output, etc.) since last call. |
| debug_get_outputA | Get debuggee output (stdout/stderr) since last call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Available Debug Adapters | List of available debug adapters and their capabilities |
| Debug Sessions | List of active debug sessions |
TDQS
Scored across 17 tools
Each tool maps to a distinct debugger action: session lifecycle, breakpoint control, stepping, and inspection. The only mild ambiguity is between debug_get_pending_events (which includes output events) and debug_get_output (raw stdout/stderr), but the descriptions mostly clarify the separation.
All tools use the same debug_ prefix followed by a clear verb_noun pattern (e.g., debug_set_breakpoints, debug_step_over, debug_get_threads). The naming is highly predictable and makes the purpose of each tool easy to infer.
17 tools is slightly above the typical well-scoped range, but each tool corresponds to a necessary DAP operation. The set is not bloated; it covers a reasonable breadth of debugging functionality without obvious redundancy.
The set covers session launch/attach/disconnect, breakpoint management, execution control, stack/scope/variable inspection, evaluation, and output retrieval. Minor gaps exist, such as listing existing breakpoints or setting variable values, but core debugging workflows are adequately supported.