Skip to content
x64dbg MCP Server

x64dbg MCP Server

Released
1 views
v1.4
MIT

Summary

A native x64dbg plugin exposing 84 debugging tools and 22 event callbacks over HTTP, so an AI assistant can drive breakpoints, memory and disassembly directly.

Features

  • 84 MCP tools across breakpoints, memory, disassembly and registers
  • 22 event callbacks so the agent reacts to debugger events
  • Native zero-dependency Zig plugin — no extra runtime beside x64dbg
  • Dual transport (streamable HTTP + SSE) with bearer-token auth
  • Supports both x32 and x64 targets, auto-starting with x64dbg

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "x64dbg MCP Server" tools will be available.
{
  "mcpServers": {
    "x64dbg-mcp-server": {
      "command": "http",
      "args": [
        "http://localhost:9094/"
      ]
    }
  }
}

Description

x64dbg is the open-source Windows debugger that most reverse-engineering and crash-analysis work on Windows runs through. This plugin puts a Model Context Protocol server inside it, so an AI assistant can drive a live debugging session rather than being handed pasted output.

The surface is broad: 84 MCP tools covering breakpoints, memory reads, disassembly, register access and the rest of the debugger's functionality, plus 22 event callbacks so the agent is notified when the debuggee hits a breakpoint, throws an exception or exits — the difference between an assistant that polls and one that reacts. Both x32 and x64 targets are supported, on ports 9095 and 9094 respectively.

It is a native plugin written in Zig with zero dependencies, which matters for a debugger: there is no Python runtime or Node process to install alongside x64dbg, and no bridge to keep in sync. Installation is copying the contents of dist/ into the x64dbg root directory — the server then starts automatically when x64dbg launches, with an auto-start toggle and settings in a configuration dialog under the Plugins menu. Transport is dual, streamable HTTP plus SSE, and requests are authenticated with a bearer token rather than left open on localhost.

Useful for malware analysis, crash triage, vulnerability research and any workflow where stepping through a binary is faster than reading it, and where handing the stepping to an agent saves the analyst the round trips. MIT licensed, cross-compilable, and under active development — v1.4 fixed agent recovery after a debuggee crash.

Related MCP Servers

MCP: ripwire

by Red Hat

New

Red Hat's zero-dependency C++23 code-context engine — ranked call graphs and blast-radius analysis, indexing a repo in under half a second with no server and no database.

MCP: Graft

by Trail

New

Builds a searchable markdown graph of your repo so coding agents stop re-exploring it on every task — reported 42% fewer tokens and 46% fewer tool calls.

New

Expo's official remote MCP server — searches Expo docs, installs compatible SDK packages, triggers and monitors EAS builds, and drives iOS/Android simulators.

MCP: Hugging Face

by Hugging Face

New

Hugging Face's official MCP server — search the Hub's models, datasets and Spaces, read repository files, and call thousands of Gradio applications as tools from one remote endpoint.

Browse all MCP servers →