Use cases

People use mcp-windbg for a handful of jobs. They share the same setup, you just ask for different work. Pick the one that matches what you have:

Use case	You have	Key tools
Analyze a crash dump	A .dmp file from a crash.	open_windbg_dump, run_windbg_cmd, close_windbg_dump
Debug a remote target	A live debugging session to connect to.	open_windbg_remote, send_ctrl_break, run_windbg_cmd
Triage multiple dumps	A folder full of dumps.	list_windbg_dumps, then the crash-dump flow per file
Debug from another machine	A Windows debugging host, but you work elsewhere.	Any tool, over the HTTP transport
Redact sensitive data	Dumps with secrets or PII.	A --filter-script over any tool

Dumps vs live targets

A dump is a frozen snapshot, you read it. A remote target is a running session, you can break in and inspect it as it executes.

Every tool is described in the Tools reference, and every command-line flag in Command-line options.