REA

What REA does

REA provides MCP and CLI workflows for reverse-engineering software and inspecting application behavior. Its supported targets include native binaries, JavaScript and Electron applications, .NET assemblies, and websites. Analysis runs locally, and returned findings include evidence and limitations so an agent can distinguish observed behavior from unresolved questions.

The workflows are intended for investigations such as understanding how a feature in an installed application works, tracing relevant code, and using the resulting findings to plan or build a comparable implementation. JavaScript and Electron analysis can inspect an extracted application directory or ASAR archive and report modules, imports, Electron boundaries, and associated evidence.

How it works

An agent calls REA over MCP with a target and an investigation request. REA performs the applicable inspection and tracing work, then returns findings for the agent to explain, investigate further, or use while writing and testing code. The same workflows are available from the terminal, so an investigation can be scripted or run without an agent interface.

Native analysis can use an existing Hopper, Ghidra, or IDA installation. Static JavaScript analysis does not require a native analysis engine. Provider selection, snapshots, and native CLI commands are part of the CLI workflow.

Setup and configuration

REA requires Node.js 22.x with version 22.23.4 or newer, Node.js 24.x with version 24.22.1 or newer, or Node.js 26.12.1 or newer, together with npm. Run the setup flow with:

npx rea-agents setup

The setup process lets you choose supported agents, review proposed configuration changes, and approve them. It registers the MCP server, installs matching workflow instructions, and backs up existing configuration. Restart the agent after setup.

For terminal use, install the package globally and inspect available commands with:

npm install --global rea-agents
rea --help

A one-off JavaScript application analysis can be run with:

npx -y rea-agents@latest analyze-javascript-application /absolute/path/to/app --json

The REA_MCP_INPUT_SCHEMA_PROFILE=full setting can be added to an MCP registration when complete field guidance and nested validation details are needed. The default compact profile retains the full tool set and server validation.

Tools and capabilities

• Inspect native binaries through Hopper, Ghidra, or IDA providers.
• Analyze JavaScript and Electron application directories or ASAR archives.
• Report JavaScript modules, imports, Electron boundaries, and evidence.
• Inspect .NET assemblies and websites.
• Return findings with evidence and limitations.
• Run matching analysis workflows through MCP or the rea CLI.

Limitations and notes

Analysis is local and depends on the target and available host tools. Native analysis requires a configured provider, while static JavaScript analysis can run without a native engine. On Linux, Ghidra, JADX, firmware tool launches, and static JavaScript/Electron analysis require a procps-compatible ps executable on REA's PATH for process ownership checks. Agent setup changes require approval and the agent should be restarted afterward. Keep installations current because releases include frequent fixes; global installations can be updated with rea update.