Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"x64dbg": {
"args": [
"/c",
"npx",
"-y",
"x64dbg-mcp-server"
],
"type": "stdio",
"command": "cmd"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An MCP server that gives AI assistants full control over the x64dbg debugger. 23 mega-tools covering 151 REST endpoints via Zod discriminated unions - stepping, breakpoints, memory, disassembly, tracing, anti-debug bypasses, control flow analysis, PE dumping, and more.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'x64dbg-mcp-server' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked x64dbg-mcp-server against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in security
An evil MCP server used for redteam testing
Proof primitive for AI agents on MultiversX. Anchor file hashes on-chain as verifiable proofs.
AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.
Security-first platform for AI agents. 38 specialized agents, 15 AI-powered extensions, zero-knowledge multi-agent orchestration. SENTINEL WAF, Ed25519 auth, 2.6M grounding facts.
MCP Security Weekly
Get CVE alerts and security updates for io.github.bromoket/x64dbg and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP server that gives AI assistants full control over the x64dbg debugger. 23 mega-tools covering 151 REST endpoints via Zod discriminated unions - stepping, breakpoints, memory, disassembly, tracing, anti-debug bypasses, control flow analysis, PE dumping, and more.
Works with Claude Code, Claude Desktop, Cursor, Windsurf, Cline, and any MCP-compatible client.
x64dbg_mcp.dp64 and/or x64dbg_mcp.dp32)Copy the plugin DLLs into your x64dbg plugins directories:
x64dbg/
x64/plugins/x64dbg_mcp.dp64 <-- for 64-bit debugging
x32/plugins/x64dbg_mcp.dp32 <-- for 32-bit debugging
Start x64dbg. You should see in the log:
[MCP] x64dbg MCP Server started on 127.0.0.1:27042
Pick your client and copy the config:
Add to .claude/settings.json (project-level) or ~/.claude/settings.json (global):
{
"mcpServers": {
"x64dbg": {
"type": "stdio",
"command": "cmd",
"args": ["/c", "npx", "-y", "x64dbg-mcp-server"]
}
}
}
Add to claude_desktop_config.json:
{
"mcpServers": {
"x64dbg": {
"command": "npx",
"args": ["-y", "x64dbg-mcp-server"]
}
}
}
Add to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"x64dbg": {
"command": "npx",
"args": ["-y", "x64dbg-mcp-server"]
}
}
}
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"x64dbg": {
"command": "npx",
"args": ["-y", "x64dbg-mcp-server"]
}
}
}
Open Cline settings > MCP Servers > Configure, then add to cline_mcp_settings.json:
{
"mcpServers": {
"x64dbg": {
"command": "npx",
"args": ["-y", "x64dbg-mcp-server"]
}
}
}
The server uses stdio transport. Spawn it as a child process:
npx -y x64dbg-mcp-server
Communicate over stdin/stdout using the MCP protocol.
Open any executable in x64dbg, then talk to your AI assistant:
"Set a breakpoint on CreateFileW and run the program"
"Disassemble the current function and explain what it does"
"Search for the byte pattern 48 8B ?? 48 85 C0 in the main module"
"Hide the debugger and bypass the anti-debug checks"
"List all threads and show me which one is the anti-cheat scanner"
"Trace into the VM dispatcher and log all instructions to a file"
The system has two components:
stdio HTTP (localhost)
MCP Client <───────────────────> TypeScript MCP <──────────────────> C++
... [View full README on GitHub](https://github.com/bromoket/x64dbg_mcp#readme)