Skip to content
Back to search

x64dbg_mcp

SkillWorks with Claude CodeGitHub

Drive x64dbg with your AI. MCP server: 23 mega-tools / 153 endpoints for breakpoints, memory, disasm, tracing, anti-debug & PE dumping. Claude/Cursor/Windsurf/Cline. All local.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/bromoket--x64dbg-mcp/badge.svg)](/listings/bromoket--x64dbg-mcp)

HTML

<a href="/listings/bromoket--x64dbg-mcp"><img src="/api/listings/bromoket--x64dbg-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

1 · Plugin (inside x64dbg)

**Download** `x64dbg_mcp.dp64` / `.dp32` from the [latest release](https://github.com/bromoket/x64dbg_mcp/releases/latest) and drop them in:

x64dbg/x64/plugins/x64dbg_mcp.dp64    ← 64-bit targets
x64dbg/x32/plugins/x64dbg_mcp.dp32    ← 32-bit targets

…or **build + install** it yourself (auto-detects your x64dbg — no path editing):

.\build.ps1 -Install

Start x64dbg; the log shows `[MCP] x64dbg MCP Server started on 127.0.0.1:27042`.

2 · Server (your AI client)

No install — just point your client at npx. Claude Code:

{
  "mcpServers": {
    "x64dbg": {
      "type": "stdio",
      "command": "cmd",
      "args": ["/c", "npx", "-y", "x64dbg-mcp-server"]
    }
  }
}

Claude Desktop / Cursor / Windsurf / Cline use the same block without the `cmd /c` wrapper: `{ "command": "npx", "args": ["-y", "x64dbg-mcp-server"] }`. Full per-client paths are in the [reference](docs/REFERENCE.md#configuration).

3 · Go

Open a target in x64dbg and start talking to your assistant.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 120 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # x64dbg MCP Server
  2. [![npm version](https://img.shields.io/npm/v/x64dbg-mcp-server)](https://www.npmjs.com/package/x64dbg-mcp-server)
  3. [![MCP Registry](https://img.shields.io/badge/MCP-registry-blue)](https://registry.modelcontextprotocol.io)
  4. [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
  5. **Drive [x64dbg](https://x64dbg.com/) with your AI.** Talk to Claude, Cursor, Windsurf, Cline,
  6. or any MCP client in plain English and it sets breakpoints, reads memory, disassembles, traces,
  7. dumps PEs, and bypasses anti-debug — live, inside the debugger.
  8. **23 mega-tools** over **153 REST endpoints**, fully typed with Zod. A C++ plugin runs inside
  9. x64dbg; a tiny TypeScript server bridges it to your client over stdio. Everything stays on
  10. `127.0.0.1` — nothing leaves your machine.
  11. > **Latest — v2.3.0**
  12. > - **Hardened & crash-proof.** A malformed HTTP request can no longer crash x64dbg; the plugin
  13. > server drains connections cleanly on stop and ships an **optional auth token** (CORS is
  14. > locked down).
  15. > - **Real data from more tools.** `imports`/`exports`, `symbols` search/list, `patches` list,
  16. > and `strings` now return actual parsed results instead of pointing you at a GUI view.
  17. > - **Live trace status.** New `/api/trace/status` (+ `tracing status`) reports whether a trace
  18. > is running, and the exception/trace tools now honor every parameter they accept.
  19. > - Plus the v2.2.x fixes: x32dbg loads on current snapshots, and requests no longer time out
  20. > on long operations.
  21. >
  22. > [Download the v2.3.0 plugins →](https://github.com/bromoket/x64dbg_mcp/releases/latest)
  23. ---
  24. ## What it looks like
  25. ```
  26. "Set a breakpoint on CreateFileW and run the program"
  27. "Disassemble the current function and explain what it does"
  28. "Search for 48 8B ?? 48 85 C0 in the main module and disassemble the hits"
  29. "Hide the debugger and bypass the anti-debug checks"
  30. "Trace into the VM dispatcher and log every instruction to a file"
  31. "Dump the main module to disk and fix the import table"
  32. ```
  33. Real use: tracing VMProtect'd code, finding anti-cheat scanner threads, decoding XOR'd class
  34. names, mapping detection logic — all by asking, no manual scripting.
  35. ## Install
  36. ### 1 · Plugin (inside x64dbg)
  37. **Download** `x64dbg_mcp.dp64` / `.dp32` from the
  38. [latest release](https://github.com/bromoket/x64dbg_mcp/releases/latest) and drop them in:
  39. ```
  40. x64dbg/x64/plugins/x64dbg_mcp.dp64 ← 64-bit targets
  41. x64dbg/x32/plugins/x64dbg_mcp.dp32 ← 32-bit targets
  42. ```
  43. …or **build + install** it yourself (auto-detects your x64dbg — no path editing):
  44. ```powershell
  45. .\build.ps1 -Install
  46. ```
  47. Start x64dbg; the log shows `[MCP] x64dbg MCP Server started on 127.0.0.1:27042`.
  48. ### 2 · Server (your AI client)
  49. No install — just point your client at npx. Claude Code:
  50. ```json
  51. {
  52. "mcpServers": {
  53. "x64dbg": {
  54. "type": "stdio",
  55. "command": "cmd",
  56. "args": ["/c", "npx", "-y", "x64dbg-mcp-server"]
  57. }
  58. }
  59. }
  60. ```
  61. Claude Desktop / Cursor / Windsurf / Cline use the same block without the `cmd /c` wrapper:
  62. `{ "command": "npx", "args": ["-y", "x64dbg-mcp-server"] }`.
  63. Full per-client paths are in the [reference](docs/REFERENCE.md#configuration).
  64. ### 3 · Go
  65. Open a target in x64dbg and start talking to your assistant.
  66. ## Tools at a glance
  67. 23 action-based tools spanning the whole debugger:
  68. - **Control** — run/step/pause, raw commands, scripts, expression eval
  69. - **CPU & memory** — registers (incl. AVX-512), read/write/alloc/protect, memory map
  70. - **Stack** — call stack, SEH chain, return addresses
  71. - **Code analysis** — disassemble, assemble, xrefs, basic blocks, CFG, loops
  72. - **Breakpoints & tracing** — software/hardware/memory/conditional/logging, batch, trace logs
  73. - **Symbols & search** — labels, comments, bookmarks, AOB pattern + string scan
  74. - **Process & system** — threads/TEB, handles, TCP, PEB, **anti-debug hide**
  75. - **Patching & dumping** — byte patches, PE dump, IAT fix, patch export
  76. Every tool, action, and endpoint is documented in **[docs/REFERENCE.md](docs/REFERENCE.md)**.
  77. ## Links
  78. - **[Full reference](docs/REFERENCE.md)** — tools, architecture, build, config, troubleshooting
  79. - **[npm: x64dbg-mcp-server](https://www.npmjs.com/package/x64dbg-mcp-server)**
  80. - **[Releases](https://github.com/bromoket/x64dbg_mcp/releases)** — prebuilt plugin DLLs
  81. - **[x64dbg](https://x64dbg.com/)** — the debugger
  82. ## Security
  83. The plugin binds to `127.0.0.1` only; the server talks pure stdio. All traffic stays on
  84. localhost — no remote access, no telemetry, no data leaves your machine. For defense against
  85. other local processes, set a token in the plugin's **Settings** and pass it via
  86. `X64DBG_MCP_TOKEN` — every request must then carry it.
  87. ## Author
  88. **bromo** — [GitHub](https://github.com/bromoket). Built with
  89. [Claude Code](https://claude.ai/claude-code). [MIT](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.