Ditch the MCP protocol: export IDA output as plain text

What it does

This IDA Pro plugin flattens an entire binary database into a pile of ordinary text files: decompiled C per function, fallback assembly where the decompiler fails, strings, imports, exports, and memory hexdumps sliced into 1 MB chunks. Instead of acting as a live MCP server for an AI IDE, it batch-exports a static snapshot with caller and callee metadata baked into every file header, letting Cursor or Claude Code index and search the codebase in parallel. It is essentially glue code around IDA’s own export machinery, packaged as a single plugin script.

The interesting bit

The author’s pitch is that LLMs natively understand text, source code, and shell, so any “intelligent” middleware is just unnecessary ceremony. By refusing the MCP handshake entirely and dumping everything to disk, the tool sidesteps the lag and freezes it blames on interactive MCP modes. It is a deliberate bet that dumb bulk export beats a chatty API when you are analyzing a large binary.

Key highlights

• Each function becomes its own .c file with callers and callees annotated in the header; if decompilation fails, it automatically falls back to a matching .asm file.
• Memory is exported in 1 MB hexdump shards, while strings, imports, and exports are written as plain lookup tables.
• A progress ticker fires every 100 functions, and detailed logs track skipped library functions, fallback cases, and total failures.
• The author claims it fixes the freezing issues of the original MCP workflow and adds macOS-specific optimizations.
• The tool expects you to augment the export folder with extra context—APK labs, Frida scripts, notes—so the AI gets the “full perspective.”

Verdict

Grab it if you want to feed a binary to an AI IDE without maintaining a live bridge to IDA. If your workflow depends on real-time, interactive AI queries while stepping through a debugger, this offline approach will not help.