We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

REA

MCP server by morluto

Reverse engineer native binaries, Electron and JavaScript apps, .NET assemblies, APKs and websites from your agent or terminal.

Runs locally (Runs on your machine: its page has the install command)Runs with npx

Install REA

Runs on your machine. Your client starts it with this command:

npx -y rea-agents mcp

Needs Node.js on your computer. The setup steps below show where the command goes in each client.

Share this server

Opens this page, with the install command and setup steps.

mcp.tc/i/rea

About

REA gives an agent tools to inspect native binaries, JavaScript and Electron apps, .NET assemblies, Android APKs and devices, and websites. Results include pseudocode, assembly, strings, symbols, modules, imports and network observations, along with the evidence and limits behind each conclusion.

It runs locally over stdio from the npm package rea-agents, and the same workflows are available as a CLI. Native analysis can use an existing Hopper, Ghidra or IDA install. Node.js 22.19 or newer is required. No account or API key is documented.

What you can do

  • Decompile native binaries via Hopper, Ghidra or IDA
  • Analyze JavaScript and Electron apps, ASAR files and source maps
  • Inspect .NET assemblies, metadata and CIL
  • Analyze Android APKs and connected devices
  • Observe websites: page structure, scripts, network traffic
  • Analyze saved HAR network captures
  • Use the same tools from a terminal CLI

Tools

Local servers list their tools once they’re running, and this one doesn’t publish its list in advance. Your client shows them after you add it.

Example prompts

  • Understand how search works in the Notes app and show me the evidence.

  • Analyze this Electron app directory and list its IPC routes.

  • Decompile the main function of this binary and explain it.

  • List the manifest declarations and exported components of this APK.

Set up

Every client starts REA on your machine with the same command. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio rea -- npx -y rea-agents mcp
  1. Start Claude Code and type /mcp. rea should show as connected.

Add --scope user to make it available in every project.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "rea": {
      "command": "npx",
      "args": [
        "-y",
        "rea-agents",
        "mcp"
      ]
    }
  }
}
  1. Save the file and restart Claude Desktop.

Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "rea": {
      "command": "npx",
      "args": [
        "-y",
        "rea-agents",
        "mcp"
      ]
    }
  }
}

Needs Node.js on your computer.

VS Code

Or from a terminal:

code --add-mcp '{"name":"rea","type":"stdio","command":"npx","args":["-y","rea-agents","mcp"]}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "rea": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "rea-agents",
        "mcp"
      ]
    }
  }
}

Needs Node.js on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "rea": {
      "command": "npx",
      "args": [
        "-y",
        "rea-agents",
        "mcp"
      ]
    }
  }
}
  1. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add rea -- npx -y rea-agents mcp

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.rea]
command = "npx"
args = ["-y", "rea-agents", "mcp"]

Needs Node.js on your computer.

Gemini CLI

gemini mcp add rea npx -- -y rea-agents mcp

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

{
  "mcpServers": {
    "rea": {
      "command": "npx",
      "args": [
        "-y",
        "rea-agents",
        "mcp"
      ]
    }
  }
}

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs Node.js on your computer.

Embed

Show REA in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![REA on mcp.tc](https://mcp.tc/i/rea/badge.svg)](https://mcp.tc/i/rea)
HTML
<a href="https://mcp.tc/i/rea"><img src="https://mcp.tc/i/rea/badge.svg" alt="REA on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/rea.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/rea" title="REA on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/rea.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the REA card to your site.

Markdown
Add the mcp.tc card for REA, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/rea.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="rea"><a href="https://mcp.tc/i/rea">REA on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![REA on mcp.tc](https://mcp.tc/i/rea/badge.svg)](https://mcp.tc/i/rea)
```

Reference: https://mcp.tc/embed

Change history

This server runs on your computer, so we follow its npm package: each new version shows up here, with edits by its owner.

Follow REA and we’ll email you when something changes.

  1. , Automatic check

    New version 6.9.0 (was 6.8.0). Read from npm.

  2. , Automatic check

    New version 6.8.0 (was 6.7.0). Read from npm.

  3. , Automatic check

    New version 6.7.0 (was 6.5.0). Read from npm.

  4. , Automatic check

    New version 6.5.0 (was 6.4.0). Read from npm.

  5. , Automatic check

    Tracking started: version 6.4.0.

FAQ

Can I paste mcp.tc/i/rea into my MCP client?

No. REA runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y rea-agents mcp.

Does REA need an API key?

No. It doesn’t declare any keys or environment variables. It runs with your user account’s permissions, so check what its tools can reach.

Is REA a remote or a local server?

Local. Your client starts it as a process on your computer with npx -y rea-agents mcp, which needs Node.js.

What can REA do?

You can decompile native binaries via Hopper, Ghidra or IDA, analyze JavaScript and Electron apps, ASAR files and source maps and inspect .NET assemblies, metadata and CIL.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Does mcp.tc track changes to REA?

Partly. It runs on your computer, so we follow its npm package: its History tab shows each new version and edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read REA’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with morluto. This page was built from REA’s public metadata, last checked on 11 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.