What is x64dbg-MCP Server?
x64dbg-MCP Server is a plugin for x64dbg, the open-source Windows debugger, that runs an MCP server inside the debugger process. Connected agents can load or attach to a program, set software, hardware, memory, conditional and exception breakpoints, step and trace, read and write registers and memory, assemble patches, list modules, imports, exports, strings and cross-references, detect the original entry point of packed binaries, and dump memory or modules to disk. It also passes any x64dbg command through ExecuteDebuggerCommand.
It is written in Zig with no runtime dependencies, builds 32-bit and 64-bit plugins from one codebase, and speaks Streamable HTTP and SSE with a mandatory bearer token. Created on 22 August 2026 by the GitHub user duty1g, it has about 2,795 stars, is MIT-licensed, and released v1.7 on 3 November 2026.
How to install x64dbg-MCP Server
Copy the release dist/ folder into the x64dbg directory; connect to http://localhost:9094/ with the bearer tokenIs x64dbg-MCP Server worth it?
Static tools such as Ghidra read a binary; this one runs it. With 84 tools the agent can break at the entry point, step over calls, watch registers, follow pointer chains, trace a set number of instructions with disassembly, and set a hardware breakpoint on a memory write. For unpacking work, DetectOEP and DumpModule cover the usual find-the-real-entry-point-and-dump sequence, and WaitForEvent long-polls for breakpoints and exceptions so the agent does not spin. Being a native plugin matters: there is no Python bridge or .NET runtime between the model and the debugger API.
The security model is the point to read twice. The server can read and write process memory, allocate memory, change registers and execute arbitrary debugger commands, and it does so over unencrypted HTTP. A token is generated on first run and required on every request, and requests without it get 401 Unauthorized. The README lists 0.0.0.0, every interface, as the default listen address, while the current config.zig falls back to 127.0.0.1; check the Plugins menu after installing and keep it on loopback unless WSL or a remote client needs otherwise. Malware under analysis belongs in an isolated VM regardless.
The project is young and moving quickly: eight releases since 27 August, several of them fixing real behaviour. v1.6 made all 25 address-taking tools accept integers after Disassemble had silently fallen back to the current instruction pointer when given one; v1.7 fixed SetBookmark, which had never created a bookmark. The README's own tool count disagrees with itself (84 in the feature list, 72 in the tool section). There is one maintainer, and the Windows-only scope follows from x64dbg itself.
Where it earns its place
A malware analyst at a small incident-response firm
Unpack a packed sample to its original entry point and dump it
In an isolated Windows VM, have the agent load the sample, run DetectOEP, break there and call DumpModule, then hand the dump to a Ghidra server for static analysis. Free; saves the manual stepping.
A CTF player working a crackme
Find where the licence check compares input and why it fails
Ask the agent to search strings for the failure message, follow GetReferences to the comparison, set a conditional breakpoint and read the registers at the compare. The agent explains each step as it goes.
A Windows developer chasing a crash in a third-party DLL
Capture the call stack and arguments when an access violation hits
Set an exception breakpoint for first-chance access violations, run until it fires, then call GetCallStack, GetArguments and Disassemble around the faulting address to brief a bug report.
Before you commit
- Setup
- Copy the release's dist folder into the x64dbg directory and launch x64dbg; the server starts automatically on port 9094 (x64) or 9095 (x32). Copy the token from Plugins, then add the URL and Authorization header to the client.
- Integrations
- 84 tools and 22 debugger event callbacks over Streamable HTTP and SSE (MCP 2024-11-05). Any x64dbg command through ExecuteDebuggerCommand. Builds from source with Zig 0.16-dev on Windows, Linux, macOS or WSL.
- Data and privacy
- Runs inside x64dbg on your machine; disassembly, memory and strings go to your model provider. Full read and write control of the debugged process over plain HTTP, guarded by a token stored in mcp_config.json next to x64dbg.
- Limits
- Windows only; plain HTTP; one maintainer; README tool counts and default bind address are inconsistent with the code. GetSEHChain is x32 only.
What’s good
- 84 tools covering breakpoints, tracing, memory and PE analysis
- Native Zig plugin, no runtime to install
- Mandatory bearer token on every request
- OEP detection and module dumping for packed binaries
What’s not
- Plain HTTP; the token travels unencrypted
- README and code disagree on the default bind address
- Recent releases fixed tools that silently misbehaved
- Single maintainer, Windows only
Best for
Malware analysts, CTF players and reverse engineers who already use x64dbg and want an agent to drive the repetitive stepping, tracing and dumping in an isolated VM.
x64dbg-MCP Server alternatives
x64dbg-MCP Server: common questions
- Is x64dbg-MCP Server worth it?
- The dynamic-analysis partner to a Ghidra server: fast, dependency-free and thorough, with a plain-HTTP control channel that has full power over whatever process it is attached to. We rate it 3.9 out of 5.
- How much does x64dbg-MCP Server cost?
- Free and open source (MIT).
- What are the downsides of x64dbg-MCP Server?
- Plain HTTP; the token travels unencrypted; rEADME and code disagree on the default bind address; recent releases fixed tools that silently misbehaved; single maintainer, Windows only.
- Who is x64dbg-MCP Server best for?
- Malware analysts, CTF players and reverse engineers who already use x64dbg and want an agent to drive the repetitive stepping, tracing and dumping in an isolated VM.
- Is x64dbg-MCP Server safe for company data?
- Runs inside x64dbg on your machine; disassembly, memory and strings go to your model provider. Full read and write control of the debugged process over plain HTTP, guarded by a token stored in mcp_config.json next to x64dbg.
- What are the best x64dbg-MCP Server alternatives?
- The closest alternatives we have reviewed are GhidraMCP and REA (Reverse Engineer Anything).
Answers checked Nov 6, 2026.