REA: an MCP server that hands your coding agent a reverse engineer's tools, running on your own machine.

Python that runs on Hopper's own thread, the only place Hopper's document objects can be touched, and answers REA over an authenticated socket.

The analysis session: one active target shared by the CLI and MCP, the providers behind it, and the evidence it keeps.

One contract per tool: input schemas, examples and audited effects, kept in one place so a tool's name, schema and hints cannot drift apart.

The Hopper client: launches Hopper with the bridge injected, sends it one request at a time, and cleans up every process and file it started.

The MCP face: registers every tool, runs each call through one execute, record and deliver path, and keeps results inside the response budget.