Installation: CLI and MCP

Install heyctl

heyctl is the command line for apps on Heyo: deploy, scale, shell into VMs, read logs and manage secrets. It talks to app-lb's admin API, in a Heyo region or on hosts you run yourself.

Installer

curl -fsSL https://heyo.computer/heyctl/install.sh | sh

The installer reads a version manifest, downloads the matching build, verifies it against its sha256 digest and the SHA256SUMS inside the tarball, and installs heyctl into ~/.local/bin. Prebuilt binaries are Linux x86_64 today.

curl -fsSL https://heyo.computer/heyctl/install.sh | sh -s -- --prefix /usr/local
curl -fsSL https://heyo.computer/heyctl/install.sh | sh -s -- --list
curl -fsSL https://heyo.computer/heyctl/install.sh | HEYCTL_VERSION=0.2.0 sh
Flag / variable Purpose Default
--prefix PATH / HEYCTL_PREFIX Install into PATH/bin ~/.local
--version VER / HEYCTL_VERSION Version to install the manifest's latest
--digest SHA256 / HEYCTL_DIGEST Install this exact build and skip the manifest unset
--list Show the available versions; install nothing

From crates.io

On any platform with a Rust toolchain:

cargo install hws

The crate is the Heyo Web Services SDK; the binary it installs is heyctl.

Log in

Create a token in the dashboard at admin.us5.heyo.work: use the Get started card, or App-tokens → New token. It starts with applb_ and is confined to your namespace.

heyctl login --server https://admin.us5.heyo.work --token-stdin
heyctl whoami
heyctl get deployments

--token-stdin keeps the token out of your shell history. login saves a context named after the server; with several regions, switch between them with heyctl config use-context NAME.

The config file (~/.config/heyctl/config.json on Linux) holds your tokens in plaintext. Don't print it, paste it or commit it; heyctl config view redacts them.

Next