Get Plasm — Install open-core runtime

› Three binaries

What you install

One script pulls three release tarballs for your OS and CPU. Each binary has a distinct role in the Plasm stack.

Appliance

plasm-server

In-process plasm-agent-core kernel: one HTTP listener for discovery, execute, and Streamable MCP (/mcp). Ships packaged API plugins (ABI v4), embedded Postgres under ~/.plasm/appliance, and the Ratatui control station for MCP config, OAuth, and ops.

Then try: plasm-server

Appliance docs →

Remote client

plasm

Strict HTTP terminal against a running Plasm host (plasm-server or plasm-mcp): discovery and execute with an agent-oriented CLI (init, search, context, run). No bundled catalogs—transport-only client.

Then try: plasm init

Remote client docs →

CGS dev CLI

plasm-cgs

Schema and catalog tooling from plasm-cli: validate domain.yaml and mappings without a server. For an interactive REPL against a live HTTP API, use plasm-repl --schema (build from source).

Then try: plasm-cgs --help

Platform notes →

› Platforms

Works on your machine

Prebuilt for glibc Linux x86_64 and macOS (Apple Silicon and Intel).

macOS Apple Silicon and Intel

Linux x86_64 — Ubuntu, Debian, Fedora, and other glibc distros

Linux on ARM64: no prebuilt archive yet — use an x86_64 Linux host or build from source.
macOS first launch: if Gatekeeper blocks a binary, right-click it in Finder and choose Open, or see platform notes.

› Optional

Advanced

Install one binary, pin a version, or download tarballs manually.

Install a single binary when you do not need the full set:

bash install.sh --product appliance — plasm-server + plugins only
bash install.sh --product client — plasm only
bash install.sh --product cgs — plasm-cgs only

Other flags: --version <semver>, --install-dir <path>, --dry-run.

Download tarballs manually → Platform & install notes →