x64dbg_mcp_server_pro

What is x64dbg_mcp_server_pro?

x64dbg_mcp_server_pro is an MCP (Message Command Protocol) server that enables remote debugging of Windows executables via x64dbg, controlled directly from Visual Studio Code using the CLine and RooCode extensions. It bridges the gap between the editor and low-level debugging by allowing users to remotely control an x64dbg session, inspect memory, set breakpoints, manipulate registers, and automate analysis without leaving the editor.

How to use x64dbg_mcp_server_pro?

Download the latest release zip, unzip it, and move the extracted folder to /username/. Then edit your RooCode or CLine MCP configuration in VSCode with the provided JSON, specifying the path to the Python script (x64dbg_mcp_server_pro.py) and the x64dbg server URL (http://127.0.0.1:8888/). The server uses the stdio transport. Available MCP commands include start_debug_session, stop_debug_session, set_breakpoint, read_memory, and many more; use get_help for details.

Key features of x64dbg_mcp_server_pro

• Full debug session lifecycle control (start, stop, attach, detach)
• Execution control: continue, pause, step into/over/out
• Memory inspection and manipulation (read, write, memset)
• Word/DWord/QWord memory access (read_word, read_dword, read_qword)
• Breakpoint handling: software, hardware, and memory breakpoints
• Register manipulation and disassembly/assembly

Use cases of x64dbg_mcp_server_pro

• Remotely debug Windows executables from VSCode without switching to a separate debugger UI
• Automate breakpoint setting and memory inspection during reverse engineering sessions
• Scripted step-by-step execution and register analysis for exploit development
• Integrate low-level debugging into AI-assisted coding workflows via CLine/RooCode

FAQ from x64dbg_mcp_server_pro

What dependencies are required to run x64dbg_mcp_server_pro?

The server requires Python and a running instance of x64dbg that exposes an HTTP server (the default URL is http://127.0.0.1:8888/). The VSCode extensions CLine or RooCode are needed for the editor integration.

What transport protocol does x64dbg_mcp_server_pro use?

It uses the MCP protocol with a stdio transport, configured in the VSCode extension settings.

Are there any authentication or auto-approve settings?

The configuration includes an "autoApprove": [] field, which is empty by default. The README does not mention any built‑in authentication mechanism.

Where is the data (debug sessions, breakpoints) stored?

The README does not specify any persistent storage. Session state is likely held in the running x64dbg instance and the server process.

What are the known limits of x64dbg_mcp_server_pro?

The README does not list any specific limitations. It supports Windows executables only via x64dbg, and requires that x64dbg is already running and accessible at the configured URL.