RAD Debugger MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAD_MCP_BACKEND | No | Path to the RAD Debugger backend executable. Can also be specified with --backend <exe>. |
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 |
|---|---|
| rad_create_sessionB | Create an isolated, authenticated headless RAD backend. Does not start an application. |
| rad_list_sessionsA | List this MCP service's active debug sessions. |
| rad_list_processesA | List local Windows PIDs, executable names and parent PIDs. Select the exact application PID before attaching. |
| rad_launchB | Launch a local x64 executable with PDBs. Arguments are a list; no shell is used. Stops at entry by default. |
| rad_attachA | Attach to an existing local application PID and wait for a debug stop. May pause the application. |
| rad_get_stateB | Return current run_gen, stop_count, stop reason, processes, threads and local names. Optional full module/stack lists. |
| rad_wait_for_stopB | Wait at most 60 seconds for a NEW stop/exit. Timeout does not cancel execution. Defaults to the last execution baseline. |
| rad_set_breakpointB | Configure one breakpoint: file+line, function name, or address string. Configuration does not prove symbol resolution. |
| rad_list_breakpointsB | Read actual RAD breakpoint configuration and observed hit counts. |
| rad_remove_breakpointA | Remove a breakpoint ID returned by this session. Does not accept arbitrary config IDs. |
| rad_continueB | Resume attached processes and return a baseline for rad_wait_for_stop. |
| rad_pauseB | Pause running processes and wait for the resulting stop. |
| rad_stepB | Step the selected stopped thread at source/instruction level. Returns a new stop, exit or timeout. |
| rad_run_to_lineB | Run from the current stop to a source line, another stop, or exit. |
| rad_evaluateB | Evaluate a RAD read expression while stopped. Returns type, formatted value, messages and explicit cache/epoch evidence. |
| rad_get_stackB | Read the selected thread's native call stack, symbol names and source locations. At most 128 backend frames. |
| rad_select_contextA | Select a thread and/or reported stack frame before evaluating locals. Frame indices come from rad_get_stack. |
| rad_address_to_lineB | Resolve a virtual address to source lines in the selected process. |
| rad_open_crash_dumpB | Load a local native crash dump in an empty session. Symbol and memory coverage depend on the dump and matching PDBs. |
| rad_close_sessionA | Close RAD and detach/resume applications by default. terminate_debuggee=true explicitly terminates attached processes. |
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 20 tools
Most tools target clearly distinct actions: session lifecycle, process control, breakpoints, and inspection are well separated. Minor overlap exists between rad_create_session and rad_launch/rad_attach, and between rad_continue and rad_wait_for_stop, but descriptions clarify the relationship.
All tools use the rad_ prefix with snake_case and follow a predictable verb_noun or single-verb pattern (create_session, set_breakpoint, step, continue). The convention is uniform and immediately readable.
Twenty tools is above the typical 3-15 range, but for a full debugger domain each tool maps to a necessary operation. The set is comprehensive rather than padded, though it is on the heavy side.
The surface covers session management, launch/attach, execution control, breakpoints, stack/expression inspection, and crash dumps. Notable gaps remain around raw memory/register read-write and disassembly, which are common debugger needs but not strictly blocking for many workflows.