Thread: Ida-pro-mcp
View Single Post
  #15  
Old 09-04-2026, 01:10
Shub-Nigurrath's Avatar
Shub-Nigurrath Shub-Nigurrath is offline
VIP
 
Join Date: Mar 2004
Location: Obscure Kadath
Posts: 987
Rept. Given: 72
Rept. Rcvd 431 Times in 101 Posts
Thanks Given: 87
Thanks Rcvd at 413 Times in 131 Posts
Shub-Nigurrath Reputation: 400-499 Shub-Nigurrath Reputation: 400-499 Shub-Nigurrath Reputation: 400-499 Shub-Nigurrath Reputation: 400-499 Shub-Nigurrath Reputation: 400-499
x64dbg-mcp-server is a native plugin for x64dbg that provides debugger access via HTTP as an MCP server. The github readme offers a simple one-line client configuration:

json
{ "mcpServers": { "x64dbg": { "type": "http", "url": "http://localhost:9094/" } } }

Adding this to a project's .mcp.json file for Claude Code makes it work instantly—no authentication needed, no complications, but it's only in the project folder under .claude typically.
My goal was to make this debugger accessible not just from Claude Code, but also from Claude AI and Cowork and the Claude Desktop app. Achieving this was a different challenge, and it's worth noting the distinction. The advantage is that Claude AI consumes tokens less rapidly and you can monitor chat from the mobile too..

.mcp.json (Claude Code) understands remote HTTP/SSE MCP servers natively — the "type": "http" shape above is exactly what it expects. claude_desktop_config.json (the Claude Desktop app) is a different file for a different product, and its schema is stdio-only

I then wrote a mjs that bridges these two worlds.

The config in the claude_desktop_config.json is something like ..

PHP Code:
{
  
"mcpServers": {
    
"x64dbg-x64": {
      
"command""node.exe",
      
"args": [
        
"<path_to>\x64-x32dbg-stdio-claude-bridge.mjs",
        
"http://127.0.0.1:9094/",
        
"Authorization: Bearer <add your>"
      
]
    },
    
"x64dbg-x32": {
      
"command""node.exe",
      
"args": [
        
"<path-to>\x64-x32dbg-stdio-claude-bridge.mjs",
        
"http://127.0.0.1:9095/",
        
"Authorization: Bearer <add your>"
      
]
    }
  }, 
One UX issue: Claude asks for authorisation to fire each MCP command. You have an always-authorise command, but not an always-authorise command for the entire MCP server. This means that for very capable servers (the one I used has more than 80 commands),
you get 80 random authorisation requests. Quite annoying.

This approach has some advantages:
1. If you have x64/x32 on a machine, you can hack remotely from your phone.
2. Tasks like writing docx/pdf files and tutorials can be performed remotely.
3. Switching the engine to Ollama with a sufficiently powerful AI creates an ideal crack-machine that's untraceable
Attached Files
File Type: zip x64-x32dbg-stdio-claude-bridge.zip (2.2 KB, 0 views)
__________________
Ŝħůb-Ňìĝùŕřaŧħ ₪)
There are only 10 types of people in the world: Those who understand binary, and those who don't
http://www.accessroot.com

Last edited by Shub-Nigurrath; 09-04-2026 at 01:51.
Reply With Quote