Exetools - Ida-pro-mcp

Exetools (https://forum.exetools.com/index.php)

- General Discussion (https://forum.exetools.com/forumdisplay.php?f=2)

- - Ida-pro-mcp (https://forum.exetools.com/showthread.php?t=21233)

https://github.com/mrexodia/ida-pro-mcp

Simple MCP Server for IDA Pro , allow vibe reversing in IDA Pro.

There is a example in the page, how to solve the crackme by ida pro + vs code + cline.

Another MCP SERVER FOR IDA

https://github.com/MxIris-Reverse-Engineering/ida-mcp-server
https://github.com/taida957789/ida-mcp-server-plugin

I just learned about vibe coding apparently coined by Andrej Karpathy himself in a YouTube video. It's amazing to see how fast the AI expansion is happening in the application space. Vibe reversing might be the norm in a year or so.

Plugin interface for remote communications with Binary Ninja database and MCP server for interfacing with LLMs.

https://github.com/Invoke-RE/binja-lattice-mcp

Quote:

Originally Posted by chants (Post 132890)

could you hint what is the vid link pls?

Tweet:

Quote:

https://x.com/karpathy/status/1886192184808149383?s=19

Video:

Quote:

https://youtu.be/EWvNQjAaOHw

at 1:18:10 timestamp

By the way his last 3 videos are all excellent if wanting to learn a lot of details about LLMs and the new tech around them.

If interested in MCP servers, so many are being developed these days, here is a list:

Quote:

https://github.com/modelcontextprotocol/servers

1.4.0 released this Oct 6, 2025

What's Changed
add idalib-based MCP server by @williballenthin in #39
Add debugger mpc function by @ltlly in #46
Add functionality to list globals by @neoz in #47
Added command to find xrefs to struct fields by @JorisVanEijden in #60
add local type listing and searching function by @hoooonnam in #70
Add support for Claude Code and Small Refactoring by @Chapoly1305 in #86
List imports by @withzombies in #85
Add stack variable support by @withzombies in #81
Allow set_comment to work with no decompiler available by @withzombies in #80
Add memory read functions by @withzombies in #82
Fix member names, use defined structure builders by @withzombies in #102
Structured function disassembly by @withzombies in #96
claude code support windows now by @heheda123123 in #117
Add callee function listing feature by @nonetype in #90
Add Patch Address bytecode by @ShallowFeather in #57
Add comprehensive structure analysis functionality by @VadimBoev in #123

IDA Pro MCP is a lightweight Model Context Protocol (MCP) server that connects IDA Pro to AI assistants for automated binary analysis and reverse engineering.

What It Does
1. Natural Language Queries: Allows AI clients (like Claude, Cursor, or Cline) to read and query IDA Pro databases.
2. Automated Actions: Enables AI assistants to retrieve function info, fetch disassembly, read pseudocode, and manage comments or variable names.
3. Vibe Reversing: Facilitates conversational, interactive binary analysis workflows directly from your code editor or chat interface.

Core Architecture
1. MCP Server: Runs locally via standard input/output (stdio) or HTTP/SSE transport to receive tool calls from your AI client.
2. IDA Plugin / Backend: Communicates with IDA Pro either through an active remote control HTTP plugin or headless idalib worker processes.

When using IDA Pro MCP from mrexodia, prefer idalib interface(headless mode, no need to run IDA GUI).

And I found that if I use "npipe" protocol for cdb, it may cause OOM due to the named pipe message cache of "npfs.sys", so better use TCP protocol for cdb.
https://github.com/svnscha/mcp-windbg

x64dbg/x32dbg MCP:
https://github.com/SetsunaYukiOvO/x64dbg-mcp
https://github.com/wasdubya/x64dbgmcp

dnSpy MCP(win32/win64):
https://github.com/tuna1999/dnspy-mcp

Just ask AI Agent to install the MCPs itself, with the git repo URL.

which one do you advice?

x64dbg/x32dbg MCP:
https://github.com/SetsunaYukiOvO/x64dbg-mcp
https://github.com/wasdubya/x64dbgmcp

I highly recommend choosing wasdubya/x64dbgMCP over the other repository.

While both projects aim to provide a Model Context Protocol (MCP) server for the x64dbg debugger, wasdubya/x64dbgmcp is the more mature, widely adopted, and actively maintained implementation.

You can also ask AI agent to compare the 2 MCPs :D

Don't limit your imagination for AI agent.

Quote:

Originally Posted by Shub-Nigurrath (Post 135955)

which one do you advice?

x64dbg/x32dbg MCP:
https://github.com/SetsunaYukiOvO/x64dbg-mcp
https://github.com/wasdubya/x64dbgmcp

After a few discussions with AI, it seems that one of the several forks is probably better. large breadth of exposed services - https://github.com/duty1g/x64dbg-mcp-server

I'm also using the mcp-server from mr.exodia, atm with IDA GUI
That's not the problem, I thought about paying for anthropics claude, but before I'm testing with OpenCode and free NVIDIA Nemotron

but that's unusable, not KI tells me how algos work, I think I have to tell Nemotron how it's working

so my question, what do you do and what are you using?

I just used the above MCPs to crack 5+ apps, one of which uses Oracle GraalVM AOT compilation.

And I wrote a logical RamDisk driver which can beat Primo RamDisk with random 4KB read/write performance, with AI.

You can even use AI to do exploits to make fame and/or money :D

Quote:

Originally Posted by squareD (Post 135961)

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