REA (Reverse Engineer Anything) is an MCP server that allows you to reverse engineer software applications, binaries, and behavior in real time. The tool covers the path from application behavior to machine code, and it is convenient to use OpenCode as the agent that manages it.<\/p>\n
OpenCode is an open programming agent that lives in the terminal. It reads project files, edits code, runs commands and tests, and most importantly, it supports MCP out of the box, so REA connects to it directly.<\/p>\n
REA stands out in the field of reverse engineering with comprehensive support for several platforms and types of analysis:<\/p>\n
REA follows a three-step research process that makes reverse engineering accessible to developers:<\/p>\n
This process allows the AI \u200b\u200bagent to answer complex questions, such as: \u201cUnderstand how search works in the Notes app, show me the evidence, and create a similar feature for my project.\u201d<\/p>\n
REA can analyze Android APK files for recovery:<\/p>\n
For example, an analysis of Aegis Authenticator showed how six-digit authorization codes change every 30 seconds: it examined how time-based code generation (TOTP) works.<\/p>\n
Analysis of the % button in Windows Calculator demonstrates the capabilities of REA:<\/p>\n
REA can record a browser session and reconstruct it as an RL environment where the AI \u200b\u200bagent performs tasks like working with folders without running the original application.<\/p>\n
The DX-Ball case showed how REA restored the soundscape calculation from the 1996 Windows game by reverse-engineering C code that runs through 3,205 test cases and matches the original compiled code.<\/p>\n
REA does not give the agent ready-made conclusions without reason. The result of each query is the findings along with the evidence on which they are based. Depending on the purpose, the response includes:<\/p>\n
The agent uses this data to explain behavior, answer clarifying questions, or assemble and test its implementation. It is the presence of evidence and explicit limitations that distinguishes an REA result from a simple guess of the model.<\/p>\n
It is assumed that OpenCode is already installed and the model is connected to it. Node.js 22.23.4+, 24.22.1+ or 26.12.1+ is needed by REA itself, so check the version:<\/p>\n
node -v\n<\/code><\/pre>\n<\/div>\nStep 1: Connect REA to OpenCode<\/h2>\n
REA registers with OpenCode as an MCP server. Run in terminal:<\/p>\n
\nnpx rea-agents@latest setup\n<\/code><\/pre>\n<\/div>\nTo directly specify OpenCode, use its identifier opencode<\/code>:<\/p>\n\nnpx rea-agents@latest setup --client opencode\n<\/code><\/pre>\n<\/div>\nWhat setup does:<\/b><\/p>\n\n- registers REA as an MCP server;<\/li>\n
- adds workflow instructions;<\/li>\n
- makes a backup copy of the existing configuration;<\/li>\n
- asks for confirmation before applying changes.<\/li>\n<\/ul>\n
Important point:<\/b>
\nFor the first experiment, you can skip the optional Hopper installation. After setup is complete, restart OpenCode: exit the session and run opencode<\/code> again.<\/p>\nCheck the connection:<\/p>\n
\nnpx -y rea-agents@latest doctor --client opencode --json\n<\/code><\/pre>\n<\/div>\nSuccessful result: \"healthy\": true<\/code>.<\/p>\nThen ask the agent:<\/p>\n
\u201cCheck that REA is connected and show me which REA tools you can use.\u201d<\/p><\/blockquote>\n
Step 2: First investigation<\/h2>\n
REA can analyze applications without launching them.<\/p>\n
\n- Download the example:<\/b>\n\n
Download https:\/\/rea.tools\/examples\/notes-example.zip\n<\/code><\/pre>\n<\/div>\nUnpack the archive into the notes-example<\/code>.<\/li>\n folder<\/p>\n
- Give the agent a task:<\/b>
\n\u201cUse REA to inspect the app at \/absolute\/path\/to\/notes-example<\/code>. Find what happens when I click Export notes. Show where notes.csv is written, which fields it contains, and the relevant files and lines.\u201d<\/p><\/blockquote>\n<\/li>\n<\/ol>\nExpected response:<\/b><\/p>\n\u201cThe button sends a notes:export<\/code> message. The main process formats the notes as CSV and writes notes.csv<\/code> in the user’s Downloads folder. The columns are id<\/code> and title<\/code>.\u201d<\/p><\/blockquote>\nStep 3: Ghidra installation and native analysis<\/h2>\n
To analyze native binaries (executables and libraries), REA uses an analysis provider. The most affordable free option is Ghidra from NSA. The tool is installed once on the computer where REA runs.<\/p>\n
What you need<\/h3>\n\n- 64-bit JDK 21 or later, including Java compiler (
javac<\/code>).<\/li>\n- Ghidra archive from the releases page.<\/li>\n<\/ul>\n
Installation<\/h3>\n\n- Install 64-bit JDK 21 or later. Select a package for your computer architecture.<\/li>\n
- Download Ghidra from the Assets list on the releases page and unzip the
ghidra_\u2026_PUBLIC_\u2026.zip<\/code> archive. Take the release archive, not the \u201cSource code.\u201d<\/li>\n- Find the unpacked folder that contains
ghidraRun<\/code> or ghidraRun.bat<\/code>. This path will be needed for the GHIDRA_INSTALL_DIR<\/code> variable.<\/li>\n<\/ol>\nCheck out Java. The first command prints java.home<\/code> – this path is needed for JAVA_HOME<\/code>. The second confirms that the compiler is installed:<\/p>\n\njava -XshowSettings:properties -version\njavac -version\n<\/code><\/pre>\n<\/div>\nGhidra connection<\/h3>\n
Windows (PowerShell):<\/b><\/p>\n\n$env:GHIDRA_INSTALL_DIR = \"C:\/tools\/ghidra_12.1.4_PUBLIC\"\n$env:JAVA_HOME = \"C:\/tools\/jdk-21\"\nnpx -y rea-agents@latest doctor --provider ghidra --json\nnpx -y rea-agents@latest setup\n<\/code><\/pre>\n<\/div>\nmacOS \/ Linux:<\/b><\/p>\n\nexport GHIDRA_INSTALL_DIR=\"\/absolute\/path\/to\/ghidra_12.1.4_PUBLIC\"\nexport JAVA_HOME=\"\/absolute\/path\/to\/jdk-21\"\nnpx -y rea-agents@latest doctor --provider ghidra --json\nnpx -y rea-agents@latest setup\n<\/code><\/pre>\n<\/div>\nReplace the paths with your own. Keep the commands in one terminal session: after setting the environment variables, re-run setup, confirm the configuration update and restart OpenCode.<\/p>\n
The provider check should return a successful report:<\/p>\n
\nnpx -y rea-agents@latest doctor --provider ghidra --json\n<\/code><\/pre>\n<\/div>\nNative analysis example<\/h3>\n
Give the agent the full path to the executable file and specify the provider:<\/p>\n
\u201cUse REA with a configured provider to explore \/absolute\/path\/to\/program<\/code>. List the functions and lines, then explain the part that handles user input, with references to the code.”<\/p><\/blockquote>\nOr run the command directly from the terminal:<\/p>\n
\nnpx -y rea-agents@latest function \"\/absolute\/path\/to\/program\" main --provider ghidra --json\n<\/code><\/pre>\n<\/div>\nReplace main<\/code> with the function name or address from the target program’s list of functions. The result contains pseudocode, assembler, and references between calls.<\/p>\nAnalysis of another type of software<\/h2>\n
Select target software category:<\/p>\n
\n- JavaScript \/ Electron<\/b> – requires Node.js and npm. Guide<\/a>.<\/li>\n
- Websites<\/b> – Requires Chrome, Chromium or Edge browser. Guide<\/a>.<\/li>\n
- Android APK<\/b> – requires JADX and JDK 17+. Manual<\/a>.<\/li>\n
- Native executables<\/b> – requires Hopper, Ghidra or IDA. Guide<\/a>.<\/li>\n
- .NET assemblies<\/b> – requires Node.js and npm. Manual<\/a>.<\/li>\n<\/ul>\n
Using REA from the terminal<\/h2>\nStatic analysis of JavaScript\/Electron application<\/h3>\n\nnpx -y rea-agents@latest analyze-javascript-application \"\/absolute\/path\/to\/app\" --json\n<\/code><\/pre>\n<\/div>\nReplace the path with the folder with the application or .asar file.<\/i><\/p>\n
Where to find the Electron application .asar file:<\/b><\/p>\n\n- Windows:<\/b>
C:\\Users\\<you>\\AppData\\Local\\Programs\\<App>\\resources\\app.asar<\/code><\/li>\n- macOS:<\/b>
\/Applications\/<App>.app\/Contents\/Resources\/app.asar<\/code><\/li>\n- Linux:<\/b>
\/opt\/<App>\/resources\/app.asar<\/code><\/li>\n<\/ul>\nGlobal installation of the rea command<\/h3>\n\nnpm install --global rea-agents\n<\/code><\/pre>\n<\/div>\nAfter this, the rea --help<\/code> command is available.<\/p>\nInstallation via curl (macOS \/ Linux)<\/h3>\n\ncurl -fsSL https:\/\/raw.githubusercontent.com\/morluto\/rea\/main\/install.sh | bash\n<\/code><\/pre>\n<\/div>\nAfter installation, follow the instructions to configure the agent. If the setup menu does not appear, run rea setup<\/code>.<\/p>\nUpdate and delete<\/h2>\nREA update<\/h3>\n\nnpx rea-agents@latest setup\n<\/code><\/pre>\n<\/div>\nFor global installation: rea update<\/code><\/i><\/p>\nRemoving REA<\/h3>\n\nnpx rea-agents@latest uninstall\n<\/code><\/pre>\n<\/div>\nGetting help<\/h2>\n\n- FAQ<\/b>: rea.tools\/faq\/<\/a> – quick answers about updates, agents and analysis<\/li>\n
- Guides<\/b>: rea.tools\/guides\/<\/a> – examples for binary, Electron and browser analysis<\/li>\n
- GitHub Issues<\/b>: github.com\/morluto\/rea\/issues<\/a> – report an issue<\/li>\n
- Discord<\/b>: discord.gg\/GkcryMnJDM<\/a> – questions, investigations and work in progress<\/li>\n<\/ul>\n
Typical problems<\/h2>\nOpenCode does not see REA<\/h3>\n
Restart OpenCode after setup. Use the doctor<\/code> command to test the connection:<\/p>\n\nnpx -y rea-agents@latest doctor --client opencode --json\n<\/code><\/pre>\n<\/div>\nThe provider requires configuration<\/h3>\n
For Ghidra run:<\/p>\n
\nnpx -y rea-agents@latest doctor --provider ghidra --json\n<\/code><\/pre>\n<\/div>\nThe report will show the failed test and the suggested next step.<\/p>\n
Windows, WSL and paths with spaces<\/h3>\n\n- Use PowerShell for Windows clients<\/li>\n
- If the agent is running inside WSL, install Node.js and REA inside that Linux system and use the Linux paths<\/li>\n
- In the terminal, enclose paths with spaces in quotes<\/li>\n<\/ul>\n
Setting up Hopper on macOS<\/h3>\n
If macOS asks you to allow Automation, allow the app that runs REA in System Preferences: System Preferences \u2192 Privacy & Security \u2192 Automation, then try again.<\/p>\n
Links<\/h2>\n
https:\/\/github.com\/morluto\/rea<\/a>
\nhttps:\/\/rea.tools\/<\/a>
\nhttps:\/\/rea.tools\/get-started\/<\/a>
\nhttps:\/\/rea.tools\/guides\/<\/a>
\nhttps:\/\/opencode.ai\/<\/a>
\nhttps:\/\/opencode.ai\/docs\/<\/a>
\nhttps:\/\/opencode.ai\/docs\/mcp-servers\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"REA (Reverse Engineer Anything) is an MCP server that allows you to reverse engineer software applications, binaries, and behavior in real time. The tool covers the path from application behavior to machine code, and it is convenient to use OpenCode as the agent that manages it. OpenCode is an open programming agent that lives in […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-213","post","type-post","status-publish","format-standard","hentry","category-software"],"translation":{"provider":"WPGlobus","version":"3.0.6","language":"en","enabled_languages":["en","ru","zh","de","ja","fr","es","pt","hi"],"languages":{"en":{"title":true,"content":true,"excerpt":false},"ru":{"title":true,"content":true,"excerpt":false},"zh":{"title":true,"content":true,"excerpt":false},"de":{"title":true,"content":true,"excerpt":false},"ja":{"title":true,"content":true,"excerpt":false},"fr":{"title":true,"content":true,"excerpt":false},"es":{"title":true,"content":true,"excerpt":false},"pt":{"title":true,"content":true,"excerpt":false},"hi":{"title":true,"content":true,"excerpt":false}}},"_links":{"self":[{"href":"https:\/\/demensdeum.com\/blog\/wp-json\/wp\/v2\/posts\/213","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/demensdeum.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/demensdeum.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/demensdeum.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/demensdeum.com\/blog\/wp-json\/wp\/v2\/comments?post=213"}],"version-history":[{"count":1,"href":"https:\/\/demensdeum.com\/blog\/wp-json\/wp\/v2\/posts\/213\/revisions"}],"predecessor-version":[{"id":214,"href":"https:\/\/demensdeum.com\/blog\/wp-json\/wp\/v2\/posts\/213\/revisions\/214"}],"wp:attachment":[{"href":"https:\/\/demensdeum.com\/blog\/wp-json\/wp\/v2\/media?parent=213"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/demensdeum.com\/blog\/wp-json\/wp\/v2\/categories?post=213"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/demensdeum.com\/blog\/wp-json\/wp\/v2\/tags?post=213"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}