W
Wasdubya/x64dbgMCP
Model Context Protocol for x64dbg & x32dbg
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Source
- collected from the abordage/awesome-mcp list · type: MCP server
- Harvest history
- first seen 2026-11-05 · last seen 2026-11-14 · seen 10× · listed by 10 sources
- Score
- score 1,003 · 10 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-11-05；last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.
x64dbg MCP
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
An MCP server that can bridge various LLMS (Claude and Cursor tested) with the x64dbg debugger, providing direct access to debugging applications through prompts.
Features (Build from Source for Latest)
40+ x64dbg SDK Tools - Provides access to almost every single debugging feature given by the SDK for smart debugging.
Cross-Architecture Support - Works with both x64dbg and x32dbg.
API Compatibility - Runable from cmd using the args given in the python file.
Quick Setup in 3 Steps
1. Download Plugin
Grab .dp64 or .dp32 from this repo's build/release directory
Copy to your local: [x64dbgdir]/release/x64/plugins/
2. Configure Claude Desktop
Copy x64dbgmcp.py from this repos src directory, ensure to pip install mcp requests
Update local claudedesktopconfig.json with path to x64dbgmcp.py
json
"mcpServers": {
"x64dbg": {
"command": "Path\\To\\Python",
"args": [
"Path\\to\\x64dbg.py"
3. Start Debugging
Launch x64dbg
Start Claude Desktop
Check plugin loaded successfully (ALT+L in x64dbg for logs)
Build from Source for Latest Features!
CMake and MSVC should be installed and on PATH
git clone https://github.com/wasdubya/x64dbgmcp
cd x64dbgmcp
cmake -S . -B build (will resolve the pluginsdk automatically, so no need to worry about dependencies.)
cmake --build build --target allplugins --config Release (will build both 32 and 64 bit versions of the plugin)
TIP
1. Use the --target allplugins argument to specify both x32 and x64, otherwise use -A flag to distinguish between either x64 or Win32 build. For example 32 bit build would be:
cmake -S . -B build32 -A Win32 -DBUILDBOTHARCHES=OFF
cmake --build build32 --config Release
Usage Examples
Register inspection:
"What's the current value of RAX and RIP registers?"
Pattern searching:
"Find the pattern '48 8B 05' in the current module"
Example from Cursor
More Usage
If you do not provide the model you are working with context of where your exe is, it wont have the capabiltiy to restart the binary if it crashes or hangs. So, provide it with the full path of the binary so it can call the CMDEXEC function like "init C:\Absolute\Path\to\EXE".
Features (Build from Source for Latest)
40+ x64dbg SDK Tools - Provides access to almost every single debugging feature given by the SDK for smart debugging.
Cross-Architecture Support - Works with both x64dbg and x32dbg.
API Compatibility - Runable from cmd using the args given in the python file.
Quick Setup in 3 Steps
1. Download Plugin
Grab .dp64 or .dp32 from this repo's build/release directory
Copy to your local: [x64dbgdir]/release/x64/plugins/
2. Configure Claude Desktop
Copy x64dbgmcp.py from this repos src directory, ensure to pip install mcp requests
Update local claudedesktopconfig.json with path to x64dbgmcp.py
json
"mcpServers": {
"x64dbg": {
"command": "Path\\To\\Python",
"args": [
"Path\\to\\x64dbg.py"
3. Start Debugging
Launch x64dbg
Start Claude Desktop
Check plugin loaded successfully (ALT+L in x64dbg for logs)
Build from Source for Latest Features!
CMake and MSVC should be installed and on PATH
git clone https://github.com/wasdubya/x64dbgmcp
cd x64dbgmcp
cmake -S . -B build (will resolve the pluginsdk automatically, so no need to worry about dependencies.)
cmake --build build --target allplugins --config Release (will build both 32 and 64 bit versions of the plugin)
TIP
1. Use the --target allplugins argument to specify both x32 and x64, otherwise use -A flag to distinguish between either x64 or Win32 build. For example 32 bit build would be:
cmake -S . -B build32 -A Win32 -DBUILDBOTHARCHES=OFF
cmake --build build32 --config Release
Usage Examples
Register inspection:
"What's the current value of RAX and RIP registers?"
Pattern searching:
"Find the pattern '48 8B 05' in the current module"
Example from Cursor
More Usage
If you do not provide the model you are working with context of where your exe is, it wont have the capabiltiy to restart the binary if it crashes or hangs. So, provide it with the full path of the binary so it can call the CMDEXEC function like "init C:\Absolute\Path\to\EXE".
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/wasdubya-x64dbgmcp/)
- Source
- awesome · https://github.com/Wasdubya/x64dbgMCP
- Browse by field
- MCP servers
- Listed by
- 10 independent sources
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.