iflow-mcp_wasdubya-x64dbgmcp 1.0.0

Model Context Protocol server for x64dbg debugger

Model Context Protocol for x64dbg

An MCP server that can bridge various LLMS with the x64dbg debugger, providing direct access to debugging functionality through prompts!

Features

• 40+ x64dbg SDK Tools - Provides access to almost every debugging feature given by the SDK for smart debugging.
• Cross-Architecture Support - Works with both x64dbg and x32dbg.
• API Compatibility - (Disclaimer: As of 8-2025, Anthropic added rate limiting to their messages API, super harsh on free tiers. I recommend using models from Cursor UI)
  • Provides API access to Claude from CMD for even faster debugging and longer consecutive tool chain calls.
  • Runable from cmd using the args given in the python file. (API Key, max tool calls, etc.)
  • IF you have issues connecting to the x64dbg session from the python file, open the logs tab in x64dbg to view what port the plugin is running on and add that as the argument to your python script.

Quick Setup

1. Download Plugin

   • Grab .dp64 or .dp32 from this repo's build/release directory
   • Copy to your local: [x64dbg_dir]/release/x64/plugins/

2. Configure Claude / MCP Supported App

   • Copy x64dbgmcp.py from this repos src directory
   • Update local claude_desktop_config.json with path to x64dbgmcp.py

{
  "mcpServers": {
    "x64dbg": {
      "command": "Path\\To\\Python",
      "args": [
        "Path\\to\\x64dbg.py"
      ]
    }
  }
}

4. Start Debugging
   • Launch x64dbg
   • Start Claude Desktop
   • Check plugin loaded successfully (ALT+L in x64dbg for logs)

Build from Source

• git clone [repository-url]
• cd x64dbgmcp
• cmake -S . -B build
• cmake --build build --target all_plugins --config Release

Tips

1. Use the --target all_plugins argument to specify both x32 and x64, otherwise use -A flag to distinguish between either x64 or Win32 build. For example 32 bit build would be:

• cmake -S . -B build32 -A Win32 -DBUILD_BOTH_ARCHES=OFF
• cmake --build build32 --config Release

2. If you do not provide the model you are working with with context of where your exe is, it wont have the capabiltiy to restart the binary if it crashes or hangs. So, provide it with the full path of the binary so it can call the CMDEXEC function like "init C:\Absolute\Path\to\EXE"

This will allow for even more automated analysis.

Usage Examples

Register inspection:

"What's the current value of RAX and RIP registers?"

Pattern searching:

"Find the pattern '48 8B 05' in the current module"

Example from Cursor