REA organizes evidence from several analysis paths through a CLI and MCP interface. The available questions depend on the target, installed providers and released package version. A native pseudocode task may need Ghidra, Hopper or IDA; an Android method task may need JADX. REA helps coordinate those reads, but the underlying observations and their limits still matter.
Start with the target
Choose the actual artifact first: a native executable, APK, Electron package, website or firmware image. The same word 'inspect' can mean reading a file header, asking a decompiler for pseudocode or observing a running application. Those operations have different evidence strength. REA's target table and task-specific guides are the right place to check the exact path.
For native code, an installed analysis provider supplies function and pseudocode work. Built-in metadata readers can inspect some file structures without that provider, but their presence does not imply full decompilation. The Android package path wraps headless JADX; other Android tasks such as resources and device observation use separate tools.
Understand the two interfaces
A CLI session suits a repeatable local investigation and exportable evidence. MCP exposes tools to a configured agent client. Installing a skill or reading a prompt does not itself register the MCP server. Review the setup plan and the tool list of the connected version before relying on an agent workflow.
Keep REA's structured observations distinct from a model's prose. Save the target hash, provider, tool version, selected function or address and any limitations reported in the evidence. A summary may omit details by design, so retrieve the linked complete evidence when a conclusion depends on them.
Know the release boundary
The project's main branch documents active development. A feature on main may not be present in the package installed on your machine. Check the released package, supported Node runtime and connected server tool list for the particular operation you need. Recheck these details when the project updates; do not transfer a capability claim from one version to all versions.
Requirements & evidence
- Resource type
- Guide
- Category
- Unknown
- Host platforms
- Unknown
- Targets
- native, android, electron, web, firmware
- Level
- Intermediate
- Source checked
- 2026-11-03T04:27:22.131388+00:00
Primary sources
- https://raw.githubusercontent.com/morluto/rea/main/README.md
- https://raw.githubusercontent.com/morluto/rea/main/docs/installation.md
Source descriptions establish documented scope. They do not establish that every workflow has been reproduced by AI Craft Pad.