x64dbg MCP Server
x64dbg MCPサーバー
x64dbgの逆アセンブルおよびデバッグ機能をAIアシスタント(Claude、Windsurf Cascade、Cursorなど)に公開する、プロダクションレベルのModel Context Protocolサーバーです。
アーキテクチャ
┌─────────────────┐ STDIO/JSON-RPC ┌──────────────────┐ TCP (JSON) ┌──────────────┐
│ AI Assistant │ ◄───────────────► │ MCP Server │ ◄──────────► │ x64dbg │
│ (Claude, etc.) │ │ (Node.js / TS) │ port 27042 │ + Bridge │
└─────────────────┘ └──────────────────┘ │ Plugin │
└──────────────┘2つのコンポーネント:
MCPサーバー (
src/) — TypeScript Node.jsプロセス。STDIO経由でMCPを介してAIホストと通信し、TCP経由でブリッジに接続します。ブリッジプラグイン (
plugin/) — x64dbg内にPython 3.10+を埋め込む軽量なC言語ローダープラグイン。Pythonブリッジスクリプトはctypesを介してx64bridge.dllを直接呼び出します — x64dbgpyへの依存はありません。MCPリクエストをx64dbg Bridge SDK呼び出しに変換するローカルTCPサーバーを公開します。
Related MCP server: Binary MCP Server
機能
自動起動とPE検出
PEヘッダーを読み取ってPEアーキテクチャ(x86 / x64)を自動検出
ターゲット実行ファイルに合わせて適切なデバッガー(
x32dbgまたはx64dbg)を起動ブリッジプラグインのTCPポートが接続可能になるまで待機してから接続 — 手動設定不要
x32dbgプラグインサポート用に32ビットPython埋め込み版を同梱
コアデバッグ(12ツール)
load_executable— PEファイルの読み込み、x86/x64の自動検出、デバッガーの自動起動、エントリポイントでのブレークcontinue_execution/step_into/step_over/step_outrun_to_address— 指定アドレスまで実行set_breakpoint— ソフトウェア、ハードウェア(実行/読み取り/書き込み/アクセス)、および条件付き・ログテキスト付きメモリBPremove_breakpoint/list_breakpointsterminate_session/list_sessionsexecute_command— 未加工のx64dbgコマンドを実行
メモリとレジスタ(9ツール)
read_memory/write_memory/search_memory— ワイルドカード付き16進パターン、ASCII/Unicodeテキストget_memory_map— 保護情報とモジュール情報を含む完全な仮想メモリレイアウトget_registers/set_register— GP、フラグ、セグメント、デバッグ、FPU/SSEレジスタget_call_stack— 戻りアドレス、モジュール名、シンボルを含むバックトレースget_threads/switch_thread— スレッド列挙とコンテキスト切り替え
静的・動的解析(10ツール)
disassemble— メタデータ付き(is_call, is_jump, 参照先, コメント)analyze_function— 境界、サイズ、コールグラフ(呼び出し元+呼び出し先)、リーフ検出get_cross_references— コードおよびデータの相互参照(to/from/both)list_functions— モジュールフィルタリング、名前検索、ページネーション付きget_modules/get_imports/get_exports— DLLおよび関数名のフィルタリング付きfind_strings— コンテンツフィルタリングと最小長制御付きのASCII + Unicode検索get_pe_header— 完全なPE構造:DOS/NTヘッダー、セクション、データディレクトリ、エントロピーtrace_execution— オプションのレジスタスナップショット付き命令トレースの記録
セキュリティ分析(5ツール)
detect_packing— エントロピー分析、既知のパッカーシグネチャ、インポート数ヒューリスティック、信頼度スコアリングanalyze_suspicious_apis— 10カテゴリの100以上のマルウェア関連APIに対するインポートの相互参照detect_anti_debug— IsDebuggerPresent、タイミングチェック、PEBフラグ、TLSコールバック、int 2D/3、およびバイパス提案check_section_anomalies— W+Xセクション、異常な名前、rawサイズゼロ、高エントロピー検出generate_security_report— 全セキュリティチェックの統合された一次トリアージと全体的なリスクレベル
合計: 36ツール
前提条件
Node.js ≥ 20
Windows上にインストールされたx64dbg(または
x64dbg/配下の同梱版を使用)x64dbg用にインストールされたPython 3.10+、またはx32dbg用の同梱32ビットPython埋め込み版
ローダープラグインをビルドするための**CMake 3.15+**およびCコンパイラ(MSVC / MinGW)
インストール
# Clone and install
cd x64dbg-mcp
npm install
npm run build
# Build the loader plugin (64-bit)
cd plugin\loader
cmake -B build64 -A x64
cmake --build build64 --config Release
cd ..\..\n
# Copy plugin files into x64dbg
copy plugin\loader\build64\Release\x64dbg_mcp_loader.dp64 C:\x64dbg\plugins\
copy plugin\x64dbg_bridge_sdk.py C:\x64dbg\plugins\
copy plugin\x64dbg_mcp_bridge.py C:\x64dbg\plugins\設定
.env.exampleを.envにコピーして調整してください:
X64DBG_PATH=C:\x64dbg
BRIDGE_HOST=127.0.0.1
BRIDGE_PORT=27042
LOG_LEVEL=info
MAX_SESSIONS=5
SESSION_TIMEOUT_MS=3600000使用方法
1. AIホストの設定
注: x64dbgを手動で起動する必要はもうありません。MCPサーバーは
load_executableを呼び出すと、適切なデバッガー(x32dbgまたはx64dbg)を自動的に起動します。 ローダープラグインは自動的にPython 3を初期化し、ブリッジスクリプトを実行し、ポート27042でTCPリスナーを開始します。
Windsurf / Cascade
MCP設定に追加してください:
{
"mcpServers": {
"x64dbg-mcp": {
"command": "node",
"args": ["C:\\path\\to\\x64dbg-mcp\\dist\\server.js"],
"env": {
"BRIDGE_PORT": "27042"
}
}
}
}Claude Desktop
claude_desktop_config.jsonに追加してください:
{
"mcpServers": {
"x64dbg-mcp": {
"command": "node",
"args": ["C:\\path\\to\\x64dbg-mcp\\dist\\server.js"]
}
}
}2. デバッグの開始
AIアシスタントに次のように尋ねてください:
"Load C:\samples\target.exe and analyze it for suspicious behavior"
AIはMCPツールを使用して以下を行います:
load_executable→ バイナリを読み込むgenerate_security_report→ すべてのセキュリティチェックを実行するdisassemble→ 不審なコードを調査するset_breakpoint+continue_execution→ 動的解析を行う
ワークフロー例
クラッシュ分析
User: "My program crashes at startup, help me debug it"
AI: load_executable → continue_execution → get_call_stack →
read_memory → get_registers → disassembleマルウェアトリアージ
User: "Analyze this suspicious binary"
AI: load_executable → generate_security_report →
analyze_suspicious_apis → detect_anti_debug →
find_strings → get_imports逆アセンブル
User: "Find the license check function"
AI: load_executable → find_strings (filter: "license") →
get_cross_references → analyze_function →
disassemble → trace_executionテスト
# Test with MCP Inspector
npm run inspector
# Development mode (no build step)
npm run devプロジェクト構造
x64dbg-mcp/
├── src/
│ ├── server.ts # Entry point
│ ├── bridge.ts # TCP client to x64dbg bridge
│ ├── launcher.ts # Auto-detect PE arch & spawn debugger
│ ├── session.ts # Session lifecycle management
│ ├── config.ts # Configuration from env
│ ├── logger.ts # Winston logger (stderr only)
│ ├── types.ts # TypeScript type definitions
│ └── tools/
│ ├── index.ts # Tool registration barrel
│ ├── debug.ts # Core debugging tools
│ ├── memory.ts # Memory & register tools
│ ├── analysis.ts # Analysis tools
│ └── security.ts # Security analysis tools
├── plugin/
│ ├── x64dbg_mcp_bridge.py # TCP server + handler dispatch (Python 3)
│ ├── x64dbg_bridge_sdk.py # ctypes bindings to x64bridge.dll
│ ├── loader/
│ │ ├── x64dbg_mcp_loader.c # C plugin that embeds Python 3
│ │ └── CMakeLists.txt # Build system for the loader
│ └── README.md
├── package.json
├── tsconfig.json
├── .env.example
└── README.mdライセンス
MIT
Available Tools
39 toolsanalyze_functionA
Analyse the function that contains the given address. Returns boundaries, size, call graph (callers + callees), and whether the function is a leaf.
Inputs: sessionId (required), address (required).
analyze_suspicious_apisA
Cross-reference the executable's import table against a database of Windows APIs commonly used by malware, grouped by category (process injection, network, crypto, anti-debug, etc.). Returns per-category findings and an overall risk level.
Inputs: sessionId (required), module, includeAll.
check_section_anomaliesA
Check PE sections for anomalies that may indicate packing, code injection, or tampering: writable+executable sections, unusual names, zero raw-size with non-zero virtual-size, high entropy.
Inputs: sessionId (required), module.
close_debuggerA
Kill the x64dbg or x32dbg process. Works even if the bridge is not connected. Use this to cleanly shut down the debugger before deploying updated plugins or when you need to restart the debugger.
Inputs: force.
collect_bp_argsA
Continue execution in a loop, collecting a memory expression at each breakpoint hit. Use this to trace repeated calls (e.g. AddMoudle, GetClassObject). The default expr 'ptr_utf16@[esp+4]' reads a wchar_t* arg from the x86 stack.
Inputs: sessionId (required), expr, maxHits, timeoutSec.
continue_executionA
Resume execution of a paused debuggee. Runs until the next breakpoint, exception, or program exit. REQUIRES: session state must be 'paused' (check with get_status). Returns stopReason ('breakpoint', 'paused', or 'exited') and the address where execution stopped. If stopReason is 'exited', the process has terminated.
Inputs: sessionId (required).
detect_anti_debugB
Scan the loaded executable for common anti-debugging techniques: API checks (IsDebuggerPresent, NtQueryInformationProcess), timing checks, PEB flags, int 2d / int 3, TLS callbacks, etc.
Inputs: sessionId (required), module.
detect_packingA
Analyse the loaded executable for signs of packing or obfuscation. Checks section entropy, section name anomalies, import table size, entry-point location, and known packer signatures. Returns a confidence score and list of indicators.
Inputs: sessionId (required), module.
disassembleA
Disassemble instructions starting at a given address in the loaded module. Returns address, raw bytes, mnemonic, operands, and metadata (is_call, is_jump, reference target) for each instruction. Safe to call while paused. Address may be a hex value ('0x401000') or a symbol name ('main', 'kernel32.CreateFileW'). Tip: after load_executable with breakOnEntry=true, disassemble the entry point returned in the load result to see where execution begins.
Inputs: sessionId (required), address (required), count.
execute_commandA
Execute a raw x64dbg command string. Use this for advanced operations not covered by other tools. Returns the command output.
Inputs: sessionId (required), command (required).
find_stringsB
Search for ASCII and Unicode strings in the debuggee's memory. Optionally filter by content substring or module.
Inputs: sessionId (required), module, filter, minLength, +1 more.
generate_security_reportA
Run all security analysis tools and produce a consolidated report: packing detection, suspicious API analysis, anti-debug detection, and section anomaly checks. Useful as a first-pass triage.
Inputs: sessionId (required), module.
get_call_stackA
Get the call stack (backtrace) of the current thread. Shows return addresses, module names, and function names where available.
Inputs: sessionId (required), maxFrames.
get_cross_referencesA
Find all cross-references (xrefs) to or from the given address. Returns code references (calls/jumps) and data references (reads/writes).
Inputs: sessionId (required), address (required), direction.
get_exportsB
List all exported functions/symbols for a specific module.
Inputs: sessionId (required), module (required), nameFilter.
get_importsB
List all imported functions for a specific module. Shows DLL name, function name, ordinal, and IAT address.
Inputs: sessionId (required), module, dllFilter, functionFilter.
get_memory_mapA
Return the virtual memory map of the debuggee process: all regions with base address, size, protection, type, and associated module.
Inputs: sessionId (required), filterModule, filterProtection.
get_modulesA
List all modules (DLLs and the main EXE) loaded in the debuggee with base address, size, entry point, and file path.
Inputs: sessionId (required).
get_pe_headerA
Parse and return the PE header information for a module: DOS header, NT headers, section table, data directories, timestamp, subsystem, characteristics, etc.
Inputs: sessionId (required), module.
get_registersA
Read the current CPU register values of the active thread. Includes general-purpose registers, instruction pointer (RIP/EIP), flags, and optionally segment and debug registers. REQUIRES: session must be paused (call get_status to check). On x64: returns RAX, RBX, RCX, RDX, RSI, RDI, RSP, RBP, RIP, R8-R15. On x86: returns EAX, EBX, ECX, EDX, ESI, EDI, ESP, EBP, EIP.
Inputs: sessionId (required), includeSegment, includeDebug, includeFpu.
get_statusA
Query the current state of the debugger and active session. Returns bridge connectivity, session state (idle/paused/running/stepping/terminated), current instruction pointer, active thread, and a next-step hint. Call this whenever you are unsure what state the debugger is in before issuing step/continue/breakpoint operations. This is always safe to call — it does not change any debugger state.
Inputs: sessionId.
get_threadsB
List all threads in the debuggee process with their current state.
Inputs: sessionId (required).
list_breakpointsA
List all breakpoints in the session, including hit counts and conditions.
Inputs: sessionId (required).
list_functionsA
List recognised functions in the debuggee. Can filter by module name and/or name substring.
Inputs: sessionId (required), module, nameFilter, offset, +1 more.
list_sessionsA
List all active debugging sessions with their state and metadata.
Inputs: no named parameters.
load_executableA
START HERE — load a PE executable into x64dbg and create a debugging session. Returns a sessionId that ALL other tools require as their first parameter. Auto-detects 32-bit vs 64-bit PE and launches x32dbg or x64dbg accordingly. With breakOnEntry=true (default): execution stops at the entry point and the session state becomes 'paused' — you can immediately call step_into, get_registers, or disassemble. With breakOnEntry=false: the debuggee starts running; use set_breakpoint then continue_execution to pause it later. Only one session can be active at a time. Call terminate_session first if one exists.
Inputs: executablePath (required), commandLineArgs, breakOnEntry, autoAnalyze.
read_memoryA
Read raw bytes from the debuggee's virtual address space. Returns a hex+ASCII dump. Address must be in the debuggee's mapped memory (see get_memory_map for valid ranges). REQUIRES: session must be paused.
Inputs: sessionId (required), address (required), size.
remove_breakpointB
Remove a previously set breakpoint at the given address.
Inputs: sessionId (required), address (required).
run_to_addressA
Set a one-shot breakpoint at the given address and continue execution. Stops when the address is reached or another breakpoint/exception fires first.
Inputs: sessionId (required), address (required).
search_memoryA
Search the debuggee's memory for a byte pattern or string. Supports hex patterns with wildcards (e.g. '4D 5A ?? ??') and text strings.
Inputs: sessionId (required), pattern (required), searchType, startAddress, +2 more.
set_breakpointB
Set a breakpoint. Supports software BPs, hardware BPs (execute/read/write), and memory BPs. Optionally supply a condition expression or log text.
Inputs: sessionId (required), address (required), type, condition, +2 more.
set_registerC
Set the value of a single CPU register.
Inputs: sessionId (required), register (required), value (required).
step_intoA
Execute one or more instructions, stepping INTO function calls. REQUIRES: session state must be 'paused'. Returns the new address, disassembly, module, and key register values after stepping. Use step_over instead if you want to skip over CALL instructions.
Inputs: sessionId (required), count.
step_outA
Run until the current function returns (execute until RET). REQUIRES: session state must be 'paused'. Useful for quickly leaving a called function and returning to the caller without stepping through every instruction.
Inputs: sessionId (required).
step_overA
Execute one or more instructions, stepping OVER function calls. REQUIRES: session state must be 'paused'. If the current instruction is a CALL, the entire called function executes and control returns to the instruction after the CALL. Use step_into if you want to trace inside the called function.
Inputs: sessionId (required), count.
switch_threadA
Switch the active thread. Subsequent register/stack/step operations will apply to this thread.
Inputs: sessionId (required), threadId (required).
terminate_sessionA
Stop the debuggee process and close the debugging session. x64dbg itself stays open and ready for the next load_executable call. Call this before loading a new executable, or when analysis is complete.
Inputs: sessionId (required).
trace_executionB
Record an execution trace from the current position. Steps through instructions and records address + disassembly at each step. Stops after maxInstructions or a breakpoint.
Inputs: sessionId (required), maxInstructions, traceInto, recordRegisters, +1 more.
write_memoryA
Write bytes to the debuggee's virtual memory. Use with caution — writing to wrong addresses can crash the debuggee.
Inputs: sessionId (required), address (required), hexBytes (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 39 tools
Most tools have distinct, well-defined purposes (e.g., step_into vs step_over, disassemble vs read_memory). However, tools like analyze_function and analyze_suspicious_apis could be confused if descriptions are not read carefully, and execute_command overlaps with other tools' capabilities.
All tool names use a consistent verb_noun pattern in snake_case (e.g., analyze_function, load_executable, continue_execution). No mixed conventions or vague verbs.
39 tools is on the higher end but justified by the breadth of debugger functionality. The tool set covers execution control, memory inspection, analysis, and session management without being excessive.
The tool set provides comprehensive coverage for a debugger/analysis server: loading, stepping, breakpoints, memory, registers, modules, security analysis, session management. No obvious gaps for typical reverse engineering tasks.
Maintenance
Related MCP Connectors
Hunt zero-days by talking to binaries. 40+ tools. Hosted, OAuth + SSO, invite: hi@byteray.ai
Evidence-oriented REA + Ghidra static-analysis workflows, read-only PE32 and Delphi VMT tools.
34 security tools for AI agents: phishing links, exposure maps, DNS, SSL, PQC, history, pivots.
Connect ChatGPT, Claude, Cursor or VS Code to your Windows PC: files, terminal, browser, apps.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI-assisted reverse engineering and debugging through x64dbg integration. Provides 40+ tools for breakpoint management, memory operations, register manipulation, code analysis, process control, and advanced debugging features.22-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to analyze binaries, debug processes, and inspect kernel state using Ghidra, x64dbg, WinDbg, and ILSpyCmd.12Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to control the x64dbg debugger through natural language, providing tools for breakpoints, memory, disassembly, tracing, PE dumping, and anti-debug bypass, all locally via stdio.139MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI-driven reverse engineering with x64dbg via 71+ MCP tools for breakpoints, memory, disassembly, tracing, debug control, PE analysis, and anti-anti-debugging, supporting HTTP, SSE, and stdio transports.2MIT