x64dbgMCP

This MCP server bridges the x64dbg debugger with language model prompts to enable automated debugging workflows. It exposes the x64dbgMCP tooling through an MCP interface, allowing you to drive debugging tasks, symbol parsing, thread management, and cross-architecture operations from your preferred prompt-based workflow. The server is designed to work with Claude Desktop and Cursor in the example setup, but can be used by any prompt-driven environment that can consume MCP endpoints. Install the necessary Python dependencies and run the MCP server to start sending commands that control x64dbg via the MCP bridge.

Once running, you can issue prompts that map to x64dbg SDK tools, such as retrieving register values, performing pattern searches, listing modules, and initiating symbol-based navigation. The server supports multi-arch debugging (x64/x32) and provides features like symbol parsing with pagination and Xrefs by address or string, enabling both quick inspections and deep static/dynamic analysis through natural language prompts.

Prerequisites:

• Python 3.8+ installed on the host machine
• Access to x64dbg and your debugging targets

Step-by-step installation:

1. Install Python dependencies

   • Open a terminal and run: pip install mcp requests

2. Place MCP server script

   • Ensure you have the MCP server script (e.g., x64dbgmcp.py) in a known location.

3. Configure the MCP entry point

   • Update Path to the Python interpreter and the MCP script in your environment or editor configuration.
   • Example path (adjust to your environment): Path\to\python\python.exe and Path\to\x64dbgmcp.py

4. Run the MCP server

   • From terminal: python Path\to\x64dbgmcp.py

5. Verify operation

   • Connect your MCP client or Claude Desktop instance and ensure the server name (x64dbg) is reachable.

Environment and configuration tips:

• Ensure Python prints are unbuffered to get real-time feedback: export PYTHONUNBUFFERED=1 (or set in your environment).
• If you encounter connection issues, verify that the path to x64dbgmcp.py is correct and that Python can access the x64dbg environment.
• The server is designed to operate with x64dbg across both x64 and x32 processes; ensure your target binaries are loaded appropriately in x64dbg when testing.
• If you need to customize the command, you can point to a virtual environment's Python interpreter or wrap the call in a shell script that sets up the environment before launching the MCP script.
• For troubleshooting, check logs in the MCP client for any errors parsing responses from the Python server or failures to initialize x64dbg features.