Hypa

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

Connect your client

Local (npm)

Add in one click

Opens the app, which asks before it adds the server.

Or add it by command or config

Claude CodeTerminal
claude mcp add hypa -- npx -y @hypabolic/hypa serve
Claude Desktopclaude_desktop_config.json
{
  "mcpServers": {
    "hypa": {
      "command": "npx",
      "args": [
        "-y",
        "@hypabolic/hypa",
        "serve"
      ]
    }
  }
}
Cursor~/.cursor/mcp.json
{
  "mcpServers": {
    "hypa": {
      "command": "npx",
      "args": [
        "-y",
        "@hypabolic/hypa",
        "serve"
      ]
    }
  }
}
VS Code.vscode/mcp.json
{
  "servers": {
    "hypa": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@hypabolic/hypa",
        "serve"
      ]
    }
  }
}
Codex~/.codex/config.toml
[mcp_servers.hypa]
command = "npx"
args = ["-y", "@hypabolic/hypa", "serve"]
Gemini CLITerminal
gemini mcp add --scope user hypa npx -- -y @hypabolic/hypa serve
Local (PyPI)

Add in one click

Opens the app, which asks before it adds the server.

Or add it by command or config

Claude CodeTerminal
claude mcp add hypa -- uvx hypa serve
Claude Desktopclaude_desktop_config.json
{
  "mcpServers": {
    "hypa": {
      "command": "uvx",
      "args": [
        "hypa",
        "serve"
      ]
    }
  }
}
Cursor~/.cursor/mcp.json
{
  "mcpServers": {
    "hypa": {
      "command": "uvx",
      "args": [
        "hypa",
        "serve"
      ]
    }
  }
}
VS Code.vscode/mcp.json
{
  "servers": {
    "hypa": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "hypa",
        "serve"
      ]
    }
  }
}
Codex~/.codex/config.toml
[mcp_servers.hypa]
command = "uvx"
args = ["hypa", "serve"]
Gemini CLITerminal
gemini mcp add --scope user hypa uvx -- hypa serve

What it does

Hypa 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.

What it needs

RuntimeNode.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.

Limits

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.

Who it suits

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.

Tools 7

hypa_session
Inspect the local Hypa session and record findings, decisions and checkpoints
hypa_shell
Run a shell command and return compressed output with the exit code, or raw output on request
hypa_read
Read a file in full or as an outline, signatures or a pruned view, within a token budget
hypa_search
Search files, symbols and Hypa's indexed context
hypa_code
Query the indexed structure of the source code, such as symbols
hypa_compress
Shrink text or a saved output artifact the agent already has
hypa_mcp
Call, batch, search or inspect tools on upstream MCP servers configured in Hypa, and check their sign-in

Similar servers