github.devotd.
NewModel Context Protocol

duty1g/x64dbg-mcp-server v1.6 — HTTP-based debugger control MCP plugin

duty1g/x64dbg-mcp-server is a Zig-based plugin that lets MCP-compatible AI assistants control x64dbg over HTTP.

Repositoryduty1g/x64dbg-mcp-server ↗

x64dbg-MCP Server is a native MCP (Model Context Protocol) plugin for x64dbg that exposes the debugger's full functionality over HTTP. Connect any MCP-compatible AI assistant and control x64dbg programmatically: set breakpoints, step through code, read memory, dump registers, and more. Built with Zig — zero dependencies, single-binary output, cros

stars
★ 2.5K
Forks
288
Language
Zig
License
MIT
Latest release
v1.6
Read original source ↗View on GitHub ↗

duty1g/x64dbg-mcp-server is a native plugin that exposes the features of the debugger x64dbg over HTTP so that MCP-compatible AI assistants can control programs. The latest release published in the repository is v1.6. The provided information contains nothing about what changed in this version, so the changes cannot be identified. The repository README explains that it is written in Zig and builds into a single executable with no dependencies.

The purpose of this project is to connect AI assistants so they can call debugger functions directly and carry out reverse engineering work. According to the repository README, it provides breakpoint setting, memory reading, register dump and pattern search features, along with debugger event callbacks. It cross-compiles x86 and x64 from a single codebase, and the default ports are given as 9095 and 9094 respectively. This differs from an ordinary information-lookup tool in that it is wired into program control, not just reading debugger features.

However, the README lists the number of tools inconsistently as 84 and 72, which makes the scale hard to pin down. The code tree recorded in FACTS contains 7 source files and no test files. No performance figures or verification procedures are given either. The features that control the debugger are broad, but with only the currently published information there is not enough verification evidence to judge stability and the range of its operation.