# CLI

> The livops command — deploys, logs and variables from your terminal.

Source: https://livops.dev/en/docs/cli

`livops` is a command for managing Livops from the terminal. It works with an [API token](https://livops.dev/en/docs/api-tokens).

## Install

macOS and Linux:

```bash
curl -fsSL https://livops.uz/install.sh | sh
```

Windows (PowerShell):

```text
irm https://livops.uz/install.ps1 | iex
```

The script picks the build for your system, checks its SHA-256 checksum and puts `livops` in `~/.local/bin` (Windows: `%LOCALAPPDATA%\livops\bin`). `LIVOPS_VERSION=1.2.3` installs a specific version, `LIVOPS_INSTALL_DIR` another folder. Check with `livops --version`.

Or download by hand: the current version is in [livops.uz/cli/latest.txt](https://livops.uz/cli/latest.txt), and the files are `https://livops.uz/cli/<version>/livops_<os>_<arch>` — `os` is `linux`, `darwin` or `windows` (`.exe`), `arch` is `amd64` or `arm64` — with `checksums.txt` beside them.

## Log in

```bash
livops login
```

The command asks for a token (from the team's **Settings → API tokens**, `/<team>/settings/tokens`) and saves it in your user config folder (`~/.config/livops/token`).

In CI, skip the file and use a variable:

```bash
export LIVOPS_TOKEN=lvp_xxx
livops projects
```

## Commands

| Command | What it does |
| --- | --- |
| `livops login` | saves the API token |
| `livops projects` | the team's services: name, type, status, URL |
| `livops stacks` | projects, their environments and services |
| `livops deploy <service>` | deploys and follows the build until it finishes (live or failed) |
| `livops logs <service> [-f]` | logs of a running service; `-f` follows, `--tail N` (default 200) |
| `livops env ls <service>` | lists variables |
| `livops env set <service> K=V...` | sets variables; `--secret` (before or after the pairs) makes the values secret |
| `livops env unset <service> K...` | removes variables |
| `livops open <service>` | opens the service URL in a browser |
| `livops mcp` | serves the [MCP tools](https://livops.dev/en/docs/mcp) over stdio for AI clients |

`<service>` is a name shown by `livops projects`.

## Examples

```bash
# deploy and wait for the result
livops deploy shop-api

# follow logs live
livops logs shop-api -f

# set a secret
livops env set shop-api --secret STRIPE_KEY=sk_xxx
```

## Configuration

| Variable / flag | Meaning |
| --- | --- |
| `LIVOPS_TOKEN` | Token. If unset, the file saved by `livops login` is read. |
| `LIVOPS_API` | API URL. Defaults to `https://livops.uz/api`. |
| `--api URL` | API URL for this command only; can go anywhere in the command. |

`env unset` is not a `DELETE`; it updates the variable list — so it works with a token.

## Exit codes

| Code | Meaning |
| --- | --- |
| `0` | done |
| `1` | the API refused, the network is down, or the deploy did not go live |
| `2` | the command was typed wrong (unknown command or flag) |
| `130` | interrupted with Ctrl-C; a deploy keeps building on the server |
