OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
MCP & Tooling

X64Dbg MCP Server

X64Dbg MCP Server is a native plugin for x64dbg that exposes debugger operations over HTTP through the Model Context Protocol. It lets compatible AI assistants request actions such as loading a binary, setting breakpoints, stepping through code, reading process memory and inspecting registers. The project is written in Zig and supports x32 and x64 plugin builds.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

X64Dbg MCP Server — OpenViST project profile in MCP & Tooling.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use it when x64dbg is your debugger and you want an MCP-compatible assistant to issue documented debugging operations during interactive analysis.

Who it is for

  • Reverse engineers who use x64dbg and want an MCP-compatible assistant to interact with a debugging session.
  • Developers building agent workflows around binary analysis and debugger control.

Documented uses

  • Set breakpoints, resume or step through a target, and wait for debugger events.
  • Inspect registers, disassembly, process memory, call stacks and event logs.
  • Connect an MCP client to x64dbg using an HTTP or SSE transport.
Before you choose

Requirements & limits

The repository lists an MIT license. The plugin requires a Bearer token on every request; one is generated on first run.

  • Requires x64dbg and an MCP-compatible client; it is a plugin, not a standalone debugger.
  • Supports Streamable HTTP and SSE transports.
  • Build instructions specify Zig 0.16-dev or later; releases can also be downloaded.
  • The server's bind address and port are configurable, with documented defaults of 9094 for x64 and 9095 for x32.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Install the plugin and connect an MCP client

Deploy the x32 and x64 plugin files in x64dbg and configure an MCP client to connect to the server.

Before you start

  • x64dbg
  • An MCP-compatible client
  • A release download or Zig 0.16-dev or later if building from source

Steps

  1. Copy the contents of the release's dist/ directory into the x64dbg root folder, or build with Zig and copy the resulting dist/ contents there.

  2. Launch x64dbg; the MCP server starts automatically.

  3. Use the generated Bearer token and the server URL to configure the MCP client for Streamable HTTP, or SSE for a legacy client.

Expected outcome

The MCP client is configured to send authenticated requests to the x64dbg plugin.

Guide limitations

  • The documented default ports are 9094 for x64 and 9095 for x32.
  • For WSL or remote access, the README says to use the host IP and set the bind address to 0.0.0.0 in the configuration dialog.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
9 October 2026
Original website title
duty1g/x64dbg-mcp-server · Official homepage title · retained in its source language
How we review sourcesSuggest a correction