Marrow MCP server
Commit Nov 4, 2026A reverse engineering workbench that provides a desktop GUI for REA, enabling AI agents to analyze binaries, mobile apps, and web technologies.
Also known as utabk/marrow
- Stars
- 16
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 4, 2026
- License
- MIT
What is Marrow MCP?
Marrow is a reverse engineering workbench that provides a desktop GUI for REA, enabling AI agents to analyze binaries, mobile apps, and web technologies.
Summary generated from the project's README
About Marrow MCP server
Reverse engineers can analyze binaries, mobile apps, and web technologies through a desktop GUI that integrates with the REA engine. The workbench provides a classic code browser interface featuring a Listing with disassembly, a Decompiler, and a Function Graph. It supports a wide range of targets including native binaries, Apple bundles, Electron apps, Android APKs, .NET assemblies, and WebAssembly.
Users can interact with the analysis using an integrated AI Chat by providing an Anthropic API key for Claude models like Opus, Sonnet, or Haiku. Alternatively, the AI Hub allows connecting external MCP clients such as Claude Code or Claude Desktop via a local socket. This setup enables AI agents to execute any of the 229 REA tools, rename functions, and manage bookmarks. The analysis runs locally on your computer using tools like Ghidra for native code and JADX for Android, ensuring all data remains on your machine.
What you can do with it
- 1Analyze native binariesA developer can use the CodeBrowser to examine disassembly and decompiled C code for a specific entry point.
- 2Automate reverse engineering with agentsAn AI agent can be tasked with renaming functions and adding comments to the code during an analysis session.
- 3Inspect mobile applicationsSecurity researchers can examine Android APKs using integrated tools like JADX or Apktool.
- 4Debug running processesDevelopers can attach debuggers like LLDB or Frida to investigate live running programs.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableutabk/marrow is public and reachablegithub.com/utabk/marrow ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-04github.com/utabk/marrow ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubMarrow: Reverse Engineering Workbench
A desktop GUI for REA, with a classic code browser and all 229 REA tools in one window.
Open an app. Read it down to the marrow.
Quick start · How Marrow works · What you can open · Showcase · Screenshots · FAQ · Development
[!NOTE] Marrow (formerly REA Studio) is an independent project. REA's authors don't make or endorse it. Marrow runs the REA you install and doesn't ship a copy of its own. Get REA from morluto/rea or the rea-agents npm package.
Marrow is a reverse engineering app for macOS, Windows and Linux, built on REA. REA does the analysis through its MCP server. Marrow gives it the windows a reverse engineer expects: a Listing with the disassembly, a Decompiler, a Function Graph, the Symbol Tree, Bytes, strings, references, bookmarks and search, laid out like the classic CodeBrowser many people already know.
Native binaries open in that CodeBrowser. Apple bundles, Electron apps, web pages, Android APKs, .NET assemblies, firmware, packet captures and version comparisons each have a window of their own, and the REA Tools window lists every REA tool with a form for each one.
Everything on screen comes from REA's answers, along with the evidence and limitations REA reported. Marrow doesn't parse files itself, and when a tool fails it shows the error REA returned. Analysis runs on your own computer.
You can bring Claude into the same session in two ways. Paste your own Anthropic API key into AI Chat and talk to Claude inside Marrow, or turn on the AI hub and connect Claude Code, Claude Desktop or any other MCP client. Either way, Claude can run REA's tools, move the views, rename functions, and add comments and bookmarks while you watch, and Marrow asks you before anything reaches outside the analysis.
Quick start
Download
Get the installer for your system from the latest release:
a DMG for a Mac (Apple Silicon or Intel), an .exe installer for Windows, or an AppImage or
.deb for Linux. They aren't signed yet, so your system warns the first time you open Marrow;
the release notes say how to get past that.
What you need
- REA 6.8:
npm install --global rea-agents. It needs Node.js 22.23.4+, 24.22.1+ or 26.12.1+. - For native binaries, Ghidra 12.1.4 and JDK 21.
rea doctor --provider ghidratells you if REA can use them. Marrow looks for Ghidra where people usually put it (~/Applicationson a Mac, your home folder orC:\on Windows, your home folder or/opton Linux) and for JDK 21 in Homebrew, Program Files or/usr/lib/jvm. Tool Options > REA Engine lets you point it somewhere else.
When Marrow starts, Getting Started checks for REA, Ghidra and Java and tells you how to get whatever is missing. Help > Contents opens it again any time.
Run from source
git clone https://github.com/utabk/marrow.git
cd marrow
npm install
npm run dev
Open your first program
- Marrow starts in the Project window. Create a project with File > New Project.
- Choose File > Import File and pick a binary, for example
/bin/lson a Mac or Linux, orC:\Windows\System32\notepad.exeon Windows. For a universal macOS binary, Marrow asks which architecture to analyze. - Double-click the program to open it in the CodeBrowser. REA analyzes it with Ghidra, which takes a few seconds for a small command line tool and a couple of minutes for a big app.
- Press G to go to an address or a name such as
entry. Double-click a name in the Listing or Decompiler to follow it, and press ⌥← (Alt+← on Windows and Linux) to go back.
Bring in Claude
To chat inside Marrow, open Window > AI Chat, click API Key, and paste a key from the
Anthropic Console. You can also set ANTHROPIC_API_KEY before
starting Marrow. The key is stored encrypted with your system's key store (the macOS Keychain,
Windows' DPAPI, or GNOME Keyring or KWallet on Linux) and only Marrow's main process reads it.
Pick Claude Opus, Sonnet or Haiku from the menu at the top of the chat.
To use an agent you already have, open Window > AI Hub and turn the server on. The window shows
the command to run for Claude Code (claude mcp add marrow -- …) and the block to paste into
Claude Desktop's config. The hub listens on a local socket (a named pipe on Windows), and before
any MCP message Marrow and the connector each prove they know a secret kept in your Marrow
profile, so no other program can pose as either one. It needs no API key in Marrow.
How Marrow works
Every program you open gets its own rea mcp process, because REA keeps one open target per
connection. Marrow's main process talks to those processes over MCP on stdio. The windows get
their data from the main process through a small typed bridge and never touch files or processes
themselves. REA runs Ghidra headless for native code and calls other tools where it needs them
(otool and codesign on a Mac, adb, JADX, a browser), then sends each result back with its
evidence. AI Chat and the AI hub reach REA through the same main process, with the same checks.
flowchart LR
subgraph marrow["Marrow"]
windows["Windows<br/>Listing, Decompiler, Function Graph,<br/>Security, REA Tools, AI Chat"]
main["Main process<br/>one REA session per open program"]
hub["AI hub"]
windows <-->|"typed bridge"| main
hub <--> main
end
you(["You"]) --> windows
agent(["Your AI agent<br/>Claude Code, Claude Desktop<br/>or any MCP client"]) -->|"MCP over a local socket"| hub
main <-->|"Anthropic API, with your key"| claude(["Claude"])
main <-->|"MCP over stdio"| rea["rea mcp<br/>229 tools"]
rea --> ghidra["Ghidra, headless<br/>native analysis"]
rea --> more["Other programs REA drives<br/>otool, codesign, adb, JADX,<br/>WABT, Chrome"]
What you can open
| What you open | Where it shows up in Marrow | What you need |
|---|---|---|
| Native binaries (Mach-O, ELF, PE) | The CodeBrowser: Listing, Decompiler, Function Graph, call trees, Symbol Tree, Bytes, strings, references, bookmarks, and the Security window for Mach-O | Ghidra 12.1.4 and JDK 21 |
| Apple apps and bundles | Apple Bundle Inspector: code signatures, Objective-C and Swift metadata, Info.plist, nibs, asset catalogs, crash reports | A Mac with Xcode or its command line tools |
| JavaScript and Electron apps | JS/Electron Inspector: the app graph from an ASAR or folder, Electron fuses, live Node and Electron targets | Nothing extra |
| Websites | Web Capture: live pages over Chrome's remote debugging port, REA's browser scenarios, HAR files | A Chrome-family browser |
| Archives, installers, PE and ELF details, SQLite | Artifact Inspector | Nothing extra |
| Android APKs and devices | Android | JADX, Apktool or adb, depending on the tool |
| .NET assemblies | .NET Assembly Browser | Nothing extra |
| WebAssembly | WASM Inspector | WABT 1.0.42 |
| Firmware, logic analyzer recordings, EVM bytecode | Firmware & Signals | Binwalk or Unblob and sigrok, which REA runs on Linux only |
| Network captures | Packet Capture | TShark, which REA runs on Linux only |
| Two versions of the same thing | Version Compare | Nothing extra |
| Running processes | Debug Sessions: LLDB, Rizin, Frida and Cutter, plus GDB on Linux | The debugger you pick. Marrow asks before each run. |
| Anything else REA can do | REA Tools: all 229 tools, each with a form built from its input schema | Depends on the tool |
Tool Options > REA Engine shows which REA Marrow runs and where it found each outside program
(on PATH, or in the usual place for your system). Pick a different one in the file dialog, then
press Restart REA. Marrow passes these paths to REA as its REA_* settings:
| Program | Used for | Install on macOS |
|---|---|---|
| adb | Android devices | brew install --cask android-platform-tools |
| Apktool | Android resources | brew install apktool |
| jadx-headless-mcp 0.7.1 JAR | Android classes | see REA's docs/android-analysis.md (checksum-pinned download) |
| WABT 1.0.42 | WebAssembly | brew install wabt |
| GNU objdump | objdump views | brew install binutils |
| Rizin | Rizin commands | brew install rizin |
On Windows and Linux, install them with your usual package manager or from each project's site; Marrow finds them on PATH.
You can also choose a REA checkout's CLI script (scripts/rea.mjs) as the REA to run. When that
REA offers newer tools for an open program, such as comments and bookmarks at any address or
colored decompiler tokens, Marrow uses them.
Showcase
What's inside macOS Calculator
Open the Calculator that ships with every Mac and see that its entry point is four lines: two
setup calls and SwiftUI's App.main(). REA finds 7,594 functions, Swift and Objective-C metadata
side by side, and 84 Objective-C classes.
If you've used Marrow on something interesting, share it in Discussions with the target, what you were looking for and what you found.
Screenshots
These were taken on a Mac with a REA 6.8 checkout that adds two tools, which is why the status bar says 231 instead of 229.
CodeBrowser
/bin/ls at entry: the Listing with the disassembly, the decompiled C beside it, and the
program's sections and symbols on the left.
AI Chat
Anyone can paste their own Anthropic API key here, pick a Claude model and start asking about the open program. Claude works through the same REA tools you have and can move the views as it goes.
AI Hub
Turn the hub on and connect the agent you already use. The window gives you the exact command for Claude Code and the config for Claude Desktop, and logs every call an agent makes.
Function Graph
This is entry from /bin/ls drawn as basic blocks, with an overview of the whole function in
the corner.
Security window
The Security window reads a binary's hardening from REA's Mach-O and code signature evidence:
PIE, stack canaries, writable and executable segments, pointer authentication, signing and the
hardened runtime. It also lists imported functions like strcpy whose call sites are worth
reading. It doesn't decide whether anything is exploitable.
REA Tools
The REA Tools window lists every tool in REA's own groups. Pick one and Marrow builds its form from the tool's input schema. The answer comes back as a tree, a table, the raw JSON and the evidence REA recorded.
FAQ
No. It's an independent GUI that uses REA as its engine. It was called REA Studio while it was being built, and the name changed so nobody mistakes it for REA's own product.
Only for the AI Chat window, which talks to Claude with your own Anthropic API key. Opening and analyzing files, every REA tool and the AI hub (where your agent brings its own access) work without one.
No. REA analyzes them on your computer. If you use AI Chat or connect an agent, the model provider receives whatever Claude reads, under that provider's data policy.
Marrow shows you the code, and the Security window points at missing hardening and risky imports. Deciding whether something is a real bug still means reading the decompiled code, yourself or with Claude. Only analyze software you own or are allowed to test.
macOS (Apple Silicon and Intel), Windows 10 and 11 (64-bit), and Linux (x86-64). GitHub Actions builds and tests every change on all three, launching the app against REA each time. A few parts need a Mac: the Apple Bundle Inspector and the Security window read Mach-O files with macOS tools, and opening a universal Mach-O file uses macOS's lipo. A few REA providers (TShark, Binwalk, sigrok, GDB) run on Linux only.
A lot of reverse engineers already know the classic CodeBrowser layout, so Marrow keeps its dockable windows, menus and key bindings, with Apache-2.0 icons from the Ghidra project. The look on top of that is pixel art: the Aseprite default theme and font, which are published under CC BY 4.0, in a light and a dark version. Edit > Tool Options > Theme switches between them and sets the screen scaling. Both are credited in THIRD_PARTY_NOTICES.md.
Help > Contents (Getting Started) shows whether REA, Ghidra and Java are in place. The Console
window logs every REA call Marrow makes and REA's error when one fails. Tool Options > REA Engine
shows which REA and which outside programs are in use, and rea doctor checks REA's own setup. If it still looks wrong, open an issue with
your system, the kind of file you opened, the steps and the Console output.
Development
npm install
npm run dev # the app
npm test # unit tests
npm run test:e2e # end-to-end tests on real binaries, run offscreen
npm run dist # installers for the system you're on, in apps/desktop/dist
GitHub Actions (build.yml) builds and tests Marrow on macOS,
Windows and Linux for every push: unit tests, then the app launched against REA, once from the
build and once from the packaged installer contents, with screenshots kept as artifacts. Pushing a
v* tag publishes the installers as a release.
Nothing is signed yet. Signing on a Mac needs an Apple Developer ID (CSC_NAME and the
notarization credentials before npm run dist), and Windows needs a code signing certificate.
The icon is pixel art kept as text in apps/desktop/scripts/build-icons.mjs; run it after an
edit to regenerate every size and format. The skin (fonts, theme parts and colors) is built from
packages/ghidra-ui/skin/ by node packages/ghidra-ui/scripts/build-skin.mjs. The screenshots above come from
node apps/desktop/scripts/readme-shots.mjs, run after npm run build -w apps/desktop.
Bug reports and pull requests are welcome; CONTRIBUTING.md has the details. Questions and ideas go to Discussions.
Disclaimer
Use Marrow for lawful research, learning, interoperability and preservation, and only on software you own or are allowed to examine. You're responsible for the license terms of the software you analyze and of the tools REA runs for you.
License
MIT. Third-party material keeps its own license: the icons reused from the Ghidra project are Apache-2.0, the Aseprite theme and font are CC BY 4.0, and REA is MIT. See THIRD_PARTY_NOTICES.md.
Marrow isn't affiliated with or endorsed by REA's authors, the Ghidra project, the NSA or Igara Studio.
Marrow MCP questions
Can I use my own Claude API key?
Yes, you can paste your own Anthropic API key into the AI Chat window to talk to Claude models like Opus, Sonnet, or Haiku.
Does Marrow parse files itself?
No, Marrow relies on REA for analysis and does not parse files directly; it displays the answers and evidence reported by REA.