x64dbg_mcp
by bromoket·★ 40·Score 46
MCP server for x64dbg debugger with 23 mega-tools and 151 endpoints for reverse engineering with AI assistants.
Overview
The x64dbg_mcp server provides comprehensive AI-powered debugging capabilities by integrating with the x64dbg debugger. It consists of a C++ plugin running inside x64dbg as a REST API server and a TypeScript MCP server implementing the protocol over stdio. This architecture allows AI assistants like Claude, Cursor, and Windsurf to control debugging operations, analyze code, and perform reverse engineering tasks through 151 endpoints organized into 23 mega-tools covering debugger control, CPU/memory operations, code analysis, breakpoints, tracing, symbols, process inspection, and dumping capabilities.
Try asking AI
After installing, here are 5 things you can ask your AI assistant:
When to choose this
Choose x64dbg MCP when you need AI assistance with reverse engineering tasks, particularly when working with x64dbg and want to leverage LLMs for automated debugging, analysis, and understanding of binary behavior.
When NOT to choose this
Avoid if you need debugger support beyond x64dbg, or if you prefer GUI-based debugging tools without AI integration. The server is specifically designed for Windows debugging and won't work with other platforms.
Tools this server exposes
12 tools extracted from the READMEx64dbg_debugControl execution flow and query debugger state
x64dbg_commandExecute raw x64dbg commands, batch scripts, and expression evaluation
x64dbg_registersRead/write CPU registers including GPR, flags, and AVX-512
x64dbg_memoryFull memory operations: read, write, allocate, protect, and memory map
x64dbg_disassemblyDisassemble instructions, whole functions, or assemble new code
x64dbg_analysisCross-references, function boundaries, basic blocks, source mapping
x64dbg_breakpointsFull breakpoint management: software, hardware, memory, conditional, logging
x64dbg_symbolsSymbol resolution, labels, comments, bookmarks
x64dbg_searchAOB/byte pattern scan, string search, symbol autocomplete
x64dbg_processProcess info, PID, PEB, elevation status, debugger version
x64dbg_threadsThread enumeration, TEB access, thread control
x64dbg_dumpingPE analysis, module dumping, IAT reconstruction, patch file export
Comparable tools
Installation
Prerequisites
- **x64dbg** - [Download latest snapshot](https://github.com/x64dbg/x64dbg/releases)
- **Node.js** >= 18 - [Download](https://nodejs.org/)
- **MCP plugin** - [Download from releases](https://github.com/bromoket/x64dbg_mcp/releases) (
x64dbg_mcp.dp64and/orx64dbg_mcp.dp32)
Installation
- Copy the plugin DLLs into your x64dbg plugins directories:
x64dbg/
x64/plugins/x64dbg_mcp.dp64 <-- for 64-bit debugging
x32/plugins/x64dbg_mcp.dp32 <-- for 32-bit debugging- Start x64dbg (you should see '[MCP] x64dbg MCP Server started on 127.0.0.1:27042' in the log)
- Configure your MCP client (example for Claude Desktop):
{
"mcpServers": {
"x64dbg": {
"command": "npx",
"args": ["-y", "x64dbg-mcp-server"]
}
}
}FAQ
- Which AI clients are compatible with x64dbg_mcp?
- The server works with Claude Code, Claude Desktop, Cursor, Windsurf, Cline, and any other MCP-compatible client that supports stdio transport.
- How does the communication between the MCP server and the plugin work?
- The TypeScript MCP server communicates with the C++ plugin via HTTP localhost (127.0.0.1:27042). The plugin exposes 151 REST endpoints that the MCP server routes requests to through stdio transport.
Compare x64dbg_mcp with
Last updated · Auto-generated from public README + GitHub signals.