Files
LinusandClaude Opus 5.5 43ed5f9183 Add the REA (Reverse Engineer Anything) MCP server
REA 6.8.0 (rea-agents on npm, checked against the registry's integrity
hash) runs in its own container from the same image, because some of its
tools run the target: workspace only, no display, no capabilities, and
only an internal network with no route out. It serves MCP over HTTP and
Claude Desktop reaches it through mcp-remote, installed from a committed
lockfile. It uses the image's Ghidra 12.1.4 headless and binwalk.

run.sh creates the internal network, starts REA before Claude Desktop and
stops it when Claude Desktop's container ends. Adds a README with usage
and sources.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-02 16:43:08 +01:00

19 lines
405 B
JSON

{
"mcpServers": {
"ghidra": {
"command": "/opt/ghidra-mcp/bin/ghidra-mcp",
"args": ["--ghidra-server", "http://127.0.0.1:8080/"]
},
"rea": {
"command": "/opt/node/bin/node",
"args": [
"/opt/mcp-bridge/node_modules/mcp-remote/dist/proxy.js",
"http://rea:8765/mcp",
"--allow-http",
"--transport",
"http-only"
]
}
}
}