REA
Local reverse-engineering toolkit for binaries, apps, websites and Android devices over MCP
Local terminal workspace for coding agents, with an MCP server for shell, file reads and output compression
By Hypabolic C# Local · stdio Developer tools
55 popularity score ★ 216 ↓ 842/wk
Opens the app, which asks before it adds the server.
claude mcp add hypa -- npx -y @hypabolic/hypa serve{
"mcpServers": {
"hypa": {
"command": "npx",
"args": [
"-y",
"@hypabolic/hypa",
"serve"
]
}
}
}{
"mcpServers": {
"hypa": {
"command": "npx",
"args": [
"-y",
"@hypabolic/hypa",
"serve"
]
}
}
}{
"servers": {
"hypa": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@hypabolic/hypa",
"serve"
]
}
}
}[mcp_servers.hypa]
command = "npx"
args = ["-y", "@hypabolic/hypa", "serve"]gemini mcp add --scope user hypa npx -- -y @hypabolic/hypa serveOpens the app, which asks before it adds the server.
claude mcp add hypa -- uvx hypa serve{
"mcpServers": {
"hypa": {
"command": "uvx",
"args": [
"hypa",
"serve"
]
}
}
}{
"mcpServers": {
"hypa": {
"command": "uvx",
"args": [
"hypa",
"serve"
]
}
}
}{
"servers": {
"hypa": {
"type": "stdio",
"command": "uvx",
"args": [
"hypa",
"serve"
]
}
}
}[mcp_servers.hypa]
command = "uvx"
args = ["hypa", "serve"]gemini mcp add --scope user hypa uvx -- hypa serveHypa is mainly a terminal multiplexer built for coding agents. It keeps agent panes running after you close the terminal, lets one agent read or start other panes, and trims noisy command output (build logs, test runs, package installs) down to the errors, paths and exit codes before an agent sees it. The trimming uses fixed rules on your machine, not a language model.
Its MCP side is the `hypa serve` command, a stdio server. In version 1.0.8 the code (src/Hypa.Cli/Commands/ServeCommand.cs) registers seven tools: session state, running shell commands with compressed output, reading files in outline or signature modes, searching files and symbols, code structure queries, compressing text an agent already holds, and `hypa_mcp`, a proxy that calls tools on other MCP servers configured in Hypa. The repository's architecture note on MCP lists a different, planned set (it names hypa_context and hypa_diagnostics, which the server does not register, and leaves out hypa_mcp), so go by the list on this page.
`hypa serve --read-only` turns off mutating tools and actions, and `--tool <name>` limits the server to the tools named. Hypa also wires itself into agents through hooks and a skill (`hypa init`, `hypa integration install`), which is a separate route from the MCP server.
| Runtime | Node.js 18+orPython 3.9+ |
|---|
Linux (x64 or arm64, glibc 2.34 or newer) or macOS 12 or newer. The npm package needs Node.js 18 or newer; the PyPI package needs Python 3.9 or newer (the uvx command needs uv). Packages on npm and PyPI exist from version 1.0.1 on. Building from source needs the .NET 10 SDK. hypa_mcp needs upstream MCP servers configured in Hypa before it does anything.
Windows is not a mux host: there is no Windows mux archive and install.ps1 stops with an error; only the compression CLI can be built there from source. Alpine and other musl Linux systems are not supported. hypa_shell runs commands with a 120000 ms timeout by default (timeoutMs changes it) and refuses commands its rewrite policy denies. In --read-only mode hypa_shell is blocked. A running mux keeps the binary that started it, so after an upgrade the old mux must be stopped and started again.
Suits developers on Linux or macOS who run several coding agents in terminals and want them to spend fewer tokens on command output, read files in trimmed modes, and reach other MCP servers through one proxy tool. Everything runs locally with no cloud service. Pick something else on Windows, or if you only want a plain file or shell server without a terminal workspace around it; if you want an agent that cannot change anything, start it with --read-only.
hypa_sessionhypa_shellhypa_readhypa_searchhypa_codehypa_compresshypa_mcp