Set up x64dbg-MCP Server safely
Install the x64dbg plugin, protect the Bearer token, and only run the server on trusted networks.
- Skill Road
- Set up x64dbg-MCP Server safely
Published on 21.09.2026
The x64dbg-MCP Server gives an AI assistant full control over a running debug process: reading and writing memory, changing registers, executing code. Setup should therefore start with a deliberately uncritical target application, not production or sensitive software.
Install the plugin
Download the latest release from github.com/duty1g/x64dbg-mcp-server and copy the contents of the dist/ folder into the x64dbg root directory. The folder already contains both architecture variants (x32 and x64), so a single copy operation is enough. Restart x64dbg afterward; the plugin loads automatically and starts a local HTTP server on port 9094 (x64) or 9095 (x32).
Retrieve and protect the Bearer token
On first run, the plugin automatically generates a Bearer token. Open x64dbg-MCP Server > Configure MCP Server... in the plugins menu, copy the token using the Copy button, and store it in the MCP client as an Authorization: Bearer <token> header. Since every request without a valid token is rejected with HTTP 401, the token is the only protection mechanism — it does not belong in screenshots, chat logs, or public repositories.
Choose the bind address deliberately
Leave the bind address at 127.0.0.1 by default, so the server is only reachable from the local machine. Only switch to 0.0.0.0 if an MCP client needs to connect from WSL or another machine on the same, trusted network — and additionally secure it with a firewall rule, since the connection runs over unencrypted HTTP according to the vendor.
Practice with uncritical targets first
Load a harmless sample program instead of a production or sensitive executable first. Use it to check how the assistant sets breakpoints, reads memory, and steps through code before using the server for real malware analysis or reverse-engineering tasks with proper authorization.
Frequently asked questions
Is the x64dbg-MCP Server an official x64dbg product?
No. It is developed by duty1g as an independent community plugin and is not part of the official x64dbg core project.
Can the server change or damage processes?
Yes, it can patch memory, set registers, and execute code. Use it first on uncritical sample programs before analyzing production or sensitive software.
Is the connection to the MCP server encrypted?
No, according to the vendor communication runs over unencrypted HTTP. The server should therefore not be exposed on untrusted networks, even though a Bearer token is required.
Does the server run on Linux or macOS?
The plugin can be built from Windows, WSL, Linux, or macOS, but it only runs inside x64dbg on Windows, since x64dbg itself only runs there.
What is the server intended for?
Per the disclaimer in the repository, exclusively for legitimate reverse engineering, malware analysis, security research, and educational purposes — always with proper authorization for the software being analyzed.