x64dbg_mcp

This MCP server exposes a suite of 23 tools that bridge the x64dbg debugger with AI assistants via the MCP protocol. Running as a stdio-based server, it communicates with your MCP client (Claude Code, Claude Desktop, Cursor, Windsurf, Cline, or any MCP-compatible client) and forwards requests to the local x64dbg plugin over HTTP on 127.0.0.1:27042. The server wraps x64dbg’s debugging capabilities into REST endpoints, organized by tool families such as Debugger Control, CPU & Memory, Code Analysis, Breakpoints & Tracing, and more. Use the client to issue high-level commands like setting breakpoints, inspecting memory, disassembling code, tracing execution, and bypassing anti-debug techniques, all while the AI assistant interprets natural language or structured actions.

To start, spawn the MCP server from your client’s configuration (the quick-start guidance shows using npx to run x64dbg-mcp-server). The server will wait for the x64dbg plugin to become available, perform health checks, and attempt to reconnect if x64dbg restarts. Then you can issue actions such as x64dbg_debug with run/pause, x64dbg_memory to read or write memory, x64dbg_disassembly to inspect instructions, or x64dbg_breakpoints to manage breakpoints. The 23 mega-tools route to the underlying plugin via a standardized REST interface, with Zod-based validation ensuring parameters are correct before being sent to x64dbg.

Prerequisites:

• Node.js 18 or newer
• x64dbg installed (including the x64dbg_mcp plugin: x64dbg_mcp.dp64 / x64dbg_mcp.dp32)
• An MCP client (Claude Code, Claude Desktop, Cursor, Windsurf, Cline, etc.) or any MCP-compatible client

Step-by-step installation:

1. Install Node.js from https://nodejs.org/ (NPM is included with Node.js).

2. Install the MCP server as an executable npm package via NPX (no global install required):

npx -y x64dbg-mcp-server

This will start the server and connect to the x64dbg plugin running on 127.0.0.1:27042. If you prefer a persistent install, you can install globally and run it directly:

npm install -g x64dbg-mcp-server
x64dbg-mcp-server

3. Configure your MCP client to point at the server using the example shown in the Quick Start section of the README. For the common setup, the server name is x64dbg and the command/args are:

command: npx
args: [-y, x64dbg-mcp-server]

4. Ensure the x64dbg plugin DLLs are placed in the correct plugin directories and launch x64dbg to begin receiving requests from the MCP server.

5. Verify connectivity by running a simple action from your MCP client, such as asking for debugger state or listing threads.

Tips and common issues:

• The MCP server uses stdio transport. If you start the server manually, it should be spawned as a child process by your MCP client (no port configuration required).
• The plugin API exposed by x64dbg_mcp runs on localhost:27042. If you change the plugin port or address, update the MCP client configuration accordingly (the MCP server will retry and re-connect as needed).
• Health checks run every 15 seconds with automatic reconnection if x64dbg restarts; requests may be retried up to 3 times with exponential backoff.
• If you encounter plugin connection issues, ensure the x64dbg_mcp plugin is loaded in both 64-bit and 32-bit contexts as needed for your debugging target.
• You can use any MCP-compatible client; the server’s stdio transport means it can be spawned by the client and does not require a network port exposure.
• The 23 tools validate parameters with Zod discriminated unions to prevent invalid requests from reaching x64dbg.