PlugWiki
x64dbg-mcp-server logo

x64dbg-mcp-server, the community x64dbg MCP plugin by duty1g

CommunityRemote

Lets your AI assistant drive the x64dbg debugger: load programs, set breakpoints, step through code, and read or patch memory.

This is a community plugin for x64dbg, the free Windows debugger. Once it is in x64dbg's plugins folder, Claude Code and other assistants can load a program, break on functions, step, read registers and memory, and dump modules for you. It needs no Python or .NET and starts with x64dbg. It can also patch memory and run any debugger command, so use it inside an isolated analysis machine.

Good for

  • Malware analysts who want an assistant to step through a sample inside an isolated VM
  • Reverse engineers who want help reading disassembly, imports, strings and call stacks
  • Unpacking work: finding the original entry point and dumping the unpacked module
  • Security researchers who want logging breakpoints set up by describing them
  • Windows developers debugging a native program with a Claude Code session

Works in

1 supported · 11 should work

Tap an app to see how to set it up and any known problems.

Install x64dbg-mcp-server

Claude Code

  1. 1

    Copy this prompt.

    Add the x64dbg-mcp-server server to Claude Code. Open .mcp.json (create it if it does not exist) and merge in this entry, keeping any servers already there:
    
    {
      "mcpServers": {
        "x64dbg": {
          "type": "http",
          "url": "http://localhost:9094/",
          "headers": {
            "Authorization": "Bearer <TOKEN>"
          }
        }
      }
    }
    
    Then tell me how to load it and whether I need to sign in.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires x64dbg on Windows with the plugin installed, Token from the plugin's config dialog.

Start x64dbg first, then replace <TOKEN> with the token from Plugins, x64dbg-MCP Server, Configure MCP Server. Keep the word Bearer and the space before the token. For 32-bit programs use port 9095. From WSL or another machine, use the Windows host's IP and set the listen address to 0.0.0.0.

From the project README. Source.

Tools

  • Opens a program in the debugger to start a new session

    Opens a program in the debugger and pauses it at the system breakpoint. Any session already running is ended first.

    Try: “Load C:\samples\app.exe in the debugger”

    Runs code · LoadBinary

  • Attaches the debugger to a program that is already running

    Attaches the debugger to a running process by its process ID.

    Try: “Attach to process 4312”

    Runs code · AttachProcess

  • Says whether a program is loaded, running or paused, and where

    Shows whether a program is loaded, whether it is running or paused, its process ID, the current instruction and module.

    Try: “What is the debugger doing right now?”

    Read · GetDebugState

  • Stops the program at an address or a function such as CreateFileW

    Sets a normal breakpoint at an address or a Windows API function name, so the program pauses there.

    Try: “Break on CreateFileW”

    Write · SetBreakpoint

  • Resumes the program and waits until it pauses again

    Resumes the program and waits until it hits a breakpoint, an exception or exits, up to a timeout.

    Try: “Run until the next breakpoint”

    Runs code · run

  • Runs one instruction, stepping over calls

    Runs a single instruction and steps over any function call it meets, like F8.

    Try: “Step over the next instruction”

    Runs code · StepOver

  • Runs one instruction, going into calls

    Runs a single instruction and goes into any function call it meets, like F7.

    Try: “Step into this call”

    Runs code · StepInto

  • Runs until the current function returns

    Keeps running until the current function returns to its caller, like Ctrl+F9.

    Try: “Run until this function returns”

    Runs code · StepOut

  • Runs the program until it reaches a given address

    Sets a one-time breakpoint at an address, resumes and waits for the program to reach it.

    Try: “Run to 0x401000”

    Runs code · RunToAddress

  • Pauses the running program

    Pauses the program while it is running, like F12.

    Try: “Pause the program”

    Write · PauseDebug

  • Ends the debugging session and closes the program

    Stops debugging and terminates the program being debugged.

    Try: “Stop debugging and close it”

    Delete · StopDebug

  • Restarts the program from the beginning

    Restarts the current debugging session from the start.

    Try: “Restart the program”

    Runs code · RestartDebug

Read from the source code

Pros and cons

Good

  • Free and open source under the MIT licence.
  • One native plugin file, with no Python, Node or .NET to install.
  • Works with both 32-bit and 64-bit programs.
  • Covers stepping, breakpoints, memory, modules, threads, strings, cross-references and unpacking help.
  • A token is required on every request, and the maintainer refuses to make it optional.
  • Starts on its own when x64dbg launches.

Watch out

  • Windows only, like x64dbg itself.
  • No read-only mode.
  • The README and the code disagree on the default listen address, so check it in the config dialog.
  • Traffic is unencrypted HTTP.
  • Two security holes were fixed in versions 1.0 and 1.2, so older copies are unsafe.
  • The README's tool counts disagree with each other.

Permissions

high risk · 4 things to watch · 2 advisories

High risk

Anyone with the token can make the debugger run programs, change memory and run any x64dbg command. Keep it inside an isolated VM, bind it to 127.0.0.1, and use version 1.2 or later.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It can run any debugger command and patch memory

    The assistant can start programs, attach to processes, write memory and run raw x64dbg commands. Use it only inside an isolated analysis VM. github.com

  • Check which network address it listens on

    The README says it listens on 0.0.0.0, every network the machine is on, but the code defaults to 127.0.0.1. Check the address in the config dialog and set 127.0.0.1 unless you connect from WSL or another machine. github.com

  • Traffic is plain HTTP

    The token and debugger data travel unencrypted. Do not expose the port to untrusted networks. github.com

  • Dumps write files to disk

    Memory and module dumps save files on the debugging machine. Keep them inside the VM. github.com

Security advisories

Technical details
Turning on read-onlyNo read-only mode. Every tool, including raw debugger commands and memory writes, is available to any client holding the token.
Sign-in and keysBearer token generated on first run, stored in mcp_config.json next to the x64dbg executable.

Alternatives

Use this plugin for most x64dbg work; it needs nothing else installed. Pick bromoket's x64dbg_mcp if your client only starts local programs and cannot send a token header.

ServerOfficialRunsSign-inGitHub stars
x64dbg-mcp-serverThis pageCommunityLocalToken2.6K
x64dbg_mcp (bromoket)CommunityLocal–137

What people say

People like that a token is always required and worry about running it anywhere but an isolated lab machine.

What people like

  • A security firm's write-up highlights that a token is required on every call.
  • Bugs users report get fixed within days and credited in release notes.

Common complaints

  • On a loosely built lab network it becomes a reachable service that controls a debugger.
  • New users hit 401 errors when they leave out the Bearer prefix.

In their words

Questions

Is it free?

Yes. It is open source under the MIT licence, and x64dbg is free too.

Is it safe to use?

Only on a machine you are willing to lose. Anyone with the token can run programs, change memory and run debugger commands. Run it in an isolated VM, listen on 127.0.0.1 only, and use version 1.2 or later.

Why do I get 401 Unauthorized?

The token is missing or the header is wrong. The header must read Bearer, a space, then the token from the config dialog.

Where do I find the token?

In x64dbg, open Plugins, then x64dbg-MCP Server, then Configure MCP Server. Copy puts it on the clipboard and Generate makes a new one.

Can I connect from WSL or another computer?

Yes. Set the listen address to 0.0.0.0 in the config dialog and use the Windows machine's IP in your client. Traffic is not encrypted, so keep it on a private network.

Does it work with 32-bit programs?

Yes. The release includes a plugin for x32dbg, which listens on port 9095 instead of 9094.

Do I need Python, Node or .NET?

No. It is a single native plugin that loads into x64dbg.

x64dbg-mcp-server vs bromoket's x64dbg_mcp?

This one runs inside x64dbg and your client connects to it over a local address with a token. Bromoket's runs as a small npm program your client starts, which suits clients that cannot send headers.

How do I add it to Claude Code?

Copy the plugin into x64dbg, start x64dbg, then add the entry from the setup box above with your token.

Examples

  • Load a program, break at its entry point and inspect registers and memory

    Load calc.exe and break at the entry point, then show me the registers.

    Source
  • Find the original entry point of a packed program and dump the unpacked module

    This sample looks packed. Find its original entry point and dump the module to disk.

  • Log a register every time a function is called, without pausing

    Put a breakpoint on CreateFileW that logs the file name argument and keeps running.

Information

updated Nov 2, 2026

Publisher
Community
Transport
Streamable HTTP, SSE
Auth
API key
License
MIT
Last commit
Oct 12, 2026
Open issues
0

WebsitedownloadGitHubChangelogIssues

Other x64dbg MCP servers

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 10
  1. x64dbg-MCP Server README · github.com
  2. x64dbg-mcp-server src/core/config.zig · github.com
  3. x64dbg-MCP Server tool definitions · github.com
  4. GHSA-4478-h5jv-647m · github.com
  5. GHSA-jgj3-97w2-9v9r · github.com
  6. Unauthorized · github.com
  7. bromoket/x64dbg_mcp · github.com
  8. Agentic reverse engineering: x64dbg exposed over MCP · noze.it
  9. Optional auth + per-monitor DPI scaling · github.com
  10. Releases · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.