Skip to main content

Tools Overview

debug-mcp exposes 34 tools organized into 8 categories.

CategoryToolsWhen to use
Sessiondebug_launch, debug_attach, debug_disconnect, debug_stateStart and end debug sessions
Breakpointsbreakpoint_set, breakpoint_remove, breakpoint_list, breakpoint_enable, breakpoint_set_exception, tracepoint_set, breakpoint_wait, exception_get_contextControl where execution stops
Executiondebug_continue, debug_pause, debug_stepResume, pause, and step through code
Inspectionthreads_list, stacktrace_get, variables_get, evaluate, object_inspectExamine threads, stacks, variables, and expressions
Memorymemory_read, layout_get, references_getRead raw memory, analyze object layout, trace references
Modulesmodules_list, modules_search, types_get, members_getBrowse loaded assemblies, types, and members
Code Analysiscode_load, code_find_usages, code_find_assignments, code_get_diagnostics, code_goto_definitionStatic analysis with Roslyn (no debugger needed)
Process I/Oprocess_write_input, process_read_outputSend input and read output from the debugged process

Session State Requirements

Tools require different session states to work:

RequirementTools
No session neededdebug_launch, debug_attach, debug_state, code_load, code_find_usages, code_find_assignments, code_get_diagnostics, code_goto_definition
Active session (running or paused)debug_disconnect, breakpoint_set, breakpoint_remove, breakpoint_list, breakpoint_enable, breakpoint_set_exception, tracepoint_set, breakpoint_wait, debug_continue, debug_pause, modules_list, modules_search, types_get, members_get, process_write_input, process_read_output
Paused sessiondebug_step, threads_list, stacktrace_get, variables_get, evaluate, object_inspect, memory_read, layout_get, references_get, exception_get_context