It looks like it is using "Microsoft Console Debugger (CDB)" as the interface to windbg. Just had a quick look at the code: https://github.com/svnscha/mcp-wind

It looks like it is using "Microsoft Console Debugger (CDB)" as the interface to windbg. Just had a quick look at the code: https://github.com/svnscha/mcp-windbg/blob/main/src/mcp_server_windbg/server.py https://github.com/svnscha/mcp-windbg/blob/main/src/mcp_serv... I might be wrong, but at first glance I don't think it is only using those 4 commands. It might be using them internally to get context to pass to the AI agent, but it looks like it exposes: - open_windbg_dump - run_windbg_cmd - close_windbg_dump - list_windbg_dumps The most interesting one is "run_windbg_cmd" because it might allow the MCP server to send whatever the AI agent wants. E.g: elif name == "run_windbg_cmd": args = RunWindbgCmdParams(**arguments) session = get_or_create_session( args.dump_path, cdb_path, symbols_path, timeout, verbose ) output = session.send_command(args.command) return [TextContent( type="text", text=f"Command: {args.command}\n\nOutput:\n```\n" + "\n".join(output) + "\n```" )] (edit: formatting)