Radar
← All projectsMonday, October 5, 2026
REA
Reverse engineer any app with your coding agent — one CLI and MCP server from binary behavior down to native code.
Why it matters
REA (Reverse Engineer Anything) is a local CLI and MCP server that hands reverse-engineering tools to coding agents. Setup wires Claude Code, Codex, Cursor, Gemini CLI, Windsurf, and more with an aligned skill. The agent opens binaries or apps, recovers pseudocode and strings through Hopper or bring-your-own Ghidra, follows call graphs, and keeps reproducible Evidence records. It also covers managed PE triage, passive website and Electron observation, and JavaScript or source-map reconstruction — without uploading the app to a hosted service.
Founders copy product ideas by guessing from the UI. REA lets the agent inspect a real app — even without source — explain how a feature works with evidence, then rebuild a version for your stack in the same session. That is a capability gap no generic coding harness fills: investigation tools under the agent, not another chat wrapper.
How it works
Run npx --yes rea-agents@latest setup, approve the plan, and restart the configured agent. Ask it to investigate an app or path, or use the CLI: rea doctor, rea analyze /path/to/app, rea decompile. Deep native work uses Hopper (demo or license) or a local Ghidra install you point at. MCP exposes open_binary, search, xrefs, decompile, call graphs, and function dossiers so the agent can walk a feature end to end, then write adapted code with its normal tools.
Hopper and Ghidra stay expert desktop tools. REA is the agent layer on top: one install, MCP plus skill, structured evidence, and a decompile → understand → recreate loop aimed at builders who want a feature explained and ported — not reverse engineers living in a disassembler UI.
Capabilities
- MCP server / client support
Similar tools