rea-ida-adapter: bridge REA’s IDA profile to IDA Free MCP
REA’s IDA path expects a legacy **ida-pro-mcp** tool shape. **IDA Free** often speaks **ida-free-mcp** over Streamable HTTP instead. **rea-ida-adapter** is the thin Python glue — not a substitute for Hex-Rays licensing.
Who needs it. Operators on IDA Free 9.x who want REA agents to call IDA-backed tools without pretending they own IDA Pro.
How to wire. Point REA at the adapter via REA_IDA_MCP_CONFIG (per upstream adapter README). Keep IDA Free running with its MCP endpoint; the adapter translates tool names/args.
Honest limitations. String listing may be regex-derived; callers can be inferred; sha256 may be unavailable in some Free builds. Read the adapter README before promising byte-identical workflows.
Compliance. BYO IDA Free license only. This showcase does not teach cracking IDA Pro or bypassing commercial licenses. See /compare/rea-vs-ida/ and /faq/setup-vs-providers/.
How to try. (1) Install IDA Free 9.x with a valid license. (2) Run ida-free-mcp as documented by that stack. (3) Start rea-ida-adapter; set REA_IDA_MCP_CONFIG per adapter README. (4) doctor the IDA-related path. (5) Expect honest gaps: regex string lists, derived callers, sha256 sometimes unavailable.
Limits. Adapter is protocol glue — not a decompiler and not an IDA Pro crack; stars snapshot 0 (2026-10-12 fetch); Free ≠ Pro features.
Compliance
Bring-your-own IDA Free license. Adapter is protocol glue only — no crack of IDA Pro.
Takeaways
- Adapter = protocol glue, not a decompiler.
- Document capability gaps up front.
- License stays BYO — Free ≠ Pro crack.
Related on rea.run
More on-site cases