MISSION CONTROL FOR REVERSE ENGINEERING
One stdio interface · 160+ tools · Three debuggers, one mission control.
Quick Start · Architecture · Servers · Workflows · Report an Issue
Website · ctxdebug.xyz · Contact · info@ctxdebug.xyz · Status · Public alpha
Built for authorized reverse engineering, debugging and security research.
ctxdebug is an MCP server platform that connects WinDbg, IDA Pro 9.x, and x64dbg to AI coding assistants for reverse engineering and Windows security research.
One stdio interface. 160+ tools. Three debuggers, one mission control.
The idea. MCO turns your debuggers into MCP (Model Context Protocol) tool servers. You talk to Claude, Kiro, or any MCP-compatible client — it talks to your debuggers. No copy-pasting output. No switching windows. No manual data correlation between tools.
One round trip. You say "analyze this crash dump and find the root cause." MCO opens the dump in WinDbg, runs
!analyze -v, extracts the faulting address, pivots to IDA Pro to decompile the crashing function, and returns a combined report with pseudocode and caller chain.
One prompt → WinDbg opens the dump, analyzes the crash, pivots to IDA, and returns the faulting source — root cause in ~1.8s.
- Python 3.11+
- OS Windows 10 / 11
- At least one debugger — WinDbg (Windows SDK) · IDA Pro 9.x · x64dbg
git clone https://github.com/DdUdle/ctxdebug.git
cd ctxdebug
pip install -e .Individual servers:
claude mcp add windbg -- python windbg_mcp.py
claude mcp add ida -- python ida_mcp.py
claude mcp add x64dbg -- python -m agent --mcp
claude mcp add mco -- python mco_orchestrator.py
claude mcp add mco-sessions -- python mco_sessions.pyOr use the unified gateway — one server, every tool:
claude mcp add mco-gateway -- python mco_gateway.pySee mcp_config_example.json for full JSON configuration with environment variables.
Once a server is registered, ask your AI client:
Open C:\dumps\crash.dmp, run a full crash analysis,
and decompile the function at the fault address.
MCO chains windbg_open_dump → windbg_analyze_crash → mco_pivot_to_ida automatically and returns pseudocode with the caller chain.
| Capability | What it does |
|---|---|
| Real-time debugger control | Run, pause, step, and inspect a live process through x64dbg. Set breakpoints on entire API groups (memory, network, crypto, bossix) instead of one address at a time. |
| Cross-debugger pivoting | Take an address from a WinDbg crash dump and jump straight to IDA Pro decompilation, callers, and callees with one tool call. |
| Autonomous analysis agent | The x64dbg server ships an optional ReAct reasoning agent (agent_analyze) that plans and executes multi-step goals — "find the unpacking loop", "identify anti-debug checks" — chaining tool calls on its own. Works with Claude, Groq, local Ollama, or heuristics-only. |
| Persistent memory | The agent remembers packer signatures, anti-debug patterns, and past-session insights, and recalls them automatically on new targets. |
| Session recording | Every tool call can be logged to SQLite with full-text search (FTS5). Replay a timeline, diff two sessions, or export a full Markdown report. |
| Anti-debug detect & bypass | Static scan (IDA imports/patterns) + dynamic scan (x64dbg PEB/RDTSC) combined into one report, with automatic PEB patching and instruction-level bypass patches. |
- Transport — stdio JSON-RPC (MCP
2024-11-05spec) - IDA communication — HTTP REST to
localhost:2022, auto-discovers endpoint from 6 candidates - x64dbg communication — binary framing over named pipe (
X64Amagic + uint32 length + 8-byte padding + JSON) - Agent reasoning — ReAct loop with pluggable LLM backends (Claude, Groq, OpenRouter, local Ollama, or heuristics-only)
- Sessions — SQLite with FTS5 full-text search, WAL mode, thread-safe
- Gateway — spawns sub-servers as child processes, proxies all tool calls through one stdio connection
| Server | File | What it does | Tools |
|---|---|---|---|
windbg |
windbg_mcp.py |
Crash dumps, heap analysis, shadow stack, kernel debugging | 70+ |
ida |
ida_mcp.py |
Decompilation, xrefs, type recovery, binary patching | 32+ |
x64dbg |
agent/ |
Dynamic analysis, ReAct agent, anti-debug bypass, memory patching | 38+ |
mco |
mco_orchestrator.py |
Cross-debugger compound workflows | 7 |
mco-sessions |
mco_sessions.py |
Session recording, FTS search, Markdown export | 13 |
mco-gateway |
mco_gateway.py |
Unified proxy — all servers through one connection | all |
WinDbg
Needs cdb.exe from the Windows SDK. Default path:
C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\cdb.exe
Set WINDBG_MCP_CDB if your path differs. No pre-launch needed — tools open dumps or attach on demand.
IDA Pro 9.x
-
Open IDA Pro 9.x with a binary loaded.
-
In the Python console, run:
exec(open(r'path\to\mco\ida_server_plugin.py').read())
-
HTTP server starts on port
2022.
x64dbg
-
Build the C++ plugin:
cd agent\plugins build_plugin.bat
-
Copy
mco_agent.dp64to x64dbg's plugin directory. -
Restart x64dbg — the plugin exposes named pipe
\\.\pipe\x64dbg_ai_agent.
Crash → source code (one command)
mco_crash_to_source(dump_path="C:\\dumps\\crash.dmp")Opens the dump, runs !analyze -v, extracts the faulting address, decompiles the crashing function in IDA, and returns pseudocode with callers.
Anti-debug detection & bypass
mco_bossix_report()
bossix_hide() # PEB patch
bossix_patch(address) # NOP / flip JCC at checkPivot any address to pseudocode
mco_pivot_to_ida(address="0x7FF712340000")Autonomous, goal-driven analysis
agent_analyze(goal="Find the unpacking loop and identify the OEP")The agent plans a sequence of tool calls, executes them, and reports findings — with or without an LLM backend.
Session recording
session_start(name="chrome uaf analysis")
# ... do your work ...
session_end(notes="UAF at CRenderObject::Destroy")
session_export_markdown(session_id=1)| Mode | Command |
|---|---|
| Tool-only (default) | python -m agent --mcp |
| Claude reasoning | python -m agent --mcp --llm claude --api-key sk-... |
| Local Ollama | python -m agent --mcp --llm local --llm-model deepseek-r1 |
| Groq (free tier) | python -m agent --mcp --llm groq |
| OpenRouter | python -m agent --mcp --llm openrouter |
| Interactive CLI | python -m agent --cli |
| Variable | Server | Purpose |
|---|---|---|
WINDBG_MCP_CDB |
windbg | Path to cdb.exe |
IDA_MCP_HOST |
ida | IDA HTTP host (default: localhost) |
IDA_MCP_PORT |
ida | IDA HTTP port (default: 2022) |
X64DBG_PATH |
x64dbg | Path to x64dbg.exe |
X64DBG_PIPE |
x64dbg | Named pipe path |
ANTHROPIC_API_KEY |
x64dbg | Only needed with --llm claude |
GROQ_API_KEY |
x64dbg | Only needed with --llm groq |
MCO_SESSIONS_DB |
sessions | SQLite database path |
MCO_SERVERS |
gateway | Comma-separated subset of servers to enable |
mco/
├── windbg_mcp.py # WinDbg MCP server (production, 3000+ lines)
├── ida_mcp.py # IDA Pro MCP server
├── ida_server_plugin.py # IDA Python plugin (starts HTTP server)
├── mco_orchestrator.py # Cross-debugger meta-tools
├── mco_sessions.py # Session recording (SQLite + FTS5)
├── mco_gateway.py # Unified gateway proxy
├── agent/
│ ├── __main__.py # x64dbg MCP entry point + LLM backend selection
│ ├── core.py # ReAct agent (Observe → Think → Act)
│ ├── memory.py # Persistent memory store (~/.x64ai/)
│ ├── bridge.py # Named-pipe IPC to x64dbg plugin
│ ├── mcp_server.py # Tool definitions (38+)
│ ├── skills/ # Modular skill implementations
│ └── plugins/
│ ├── x64dbg_plugin.cpp
│ └── build_plugin.bat
├── mcp_config_example.json # Ready-to-use MCP client config
└── pyproject.toml
git clone https://github.com/DdUdle/ctxdebug.git
cd ctxdebug
pip install -e ".[dev]"
pytestContributions are welcome. Please open an issue before starting large changes so the approach can be discussed first.
MIT — see LICENSE.
Three debuggers. One mission control. Go for launch. 🔥


