CLI (meetily-pro)
The meetily-pro command line client: connecting, global flags, commands, and what it doesn't cover.
meetily-pro is a thin command-line client for the gateway. It is best for one-shot control from a shell or a script: check status, list meetings, start a recording, pull a summary.
Connecting
The default server is http://127.0.0.1:8420. Override it with --server or the MEETILY_PRO_SERVER env var.
Token discovery is fail-closed: the CLI tries each source in order and does not silently fall through to the next one if you named a source explicitly.
--token-file <path>--token <token>MEETILY_PRO_TOKENenv var- the loopback token file at
{app data}/pro.meetily.ai/gateway-token
If you pass --token-file and the file can't be read, the command fails with an error. It does not fall back to step 2, 3, or 4.
Global flags
| Flag | Purpose |
|---|---|
--server <url> | Target gateway. |
--token <token> | Bearer token. |
--token-file <path> | Read the token from a file. |
--json | Machine-readable output. |
--quiet | Suppress success output. Errors still print. |
Exit codes
The CLI returns 0 on success and a nonzero code on failure: 1 for a usage or server-validation error, 2 for a timeout, 3 when it cannot connect, and 4 when access is denied (401 or 403). Check the exit code, not just stdout, when scripting. See the errors reference.
Commands
Top level
| Command | What it does |
|---|---|
health | Checks the gateway is up. |
doctor | Offline environment check: which server URL and token file it resolved, whether a token was found, and a best-effort reachability ping. For license tier and scopes, use whoami. |
version | Prints the CLI version. No server call. |
whoami | Shows the caller identity for the current token. |
search <query> | Full-text search across your meeting transcripts. |
install-cli | Local install step. No server call. |
pair <host> | Pairs with a remote instance. Supports --fingerprint to pin the server's certificate. |
mcp | The MCP server command group. See AI Assistants. |
Command groups
| Group | Subcommands |
|---|---|
meetings | list, get, export, rename, delete, speaker-labels |
transcript | get |
summary | get, set, regenerate |
jobs | list, diarization, cancel, pause, resume, retry |
config | get, set (pass the body with --json-body) |
devices | list |
models | list |
recording | start, stop, pause, resume |
Examples
meetily-pro whoamimeetily-pro meetings list --limit 20 --jsonNot covered by the CLI
The CLI has no command for:
- getting or waiting on a single job
- importing audio
- reading or waiting on live recording state
- webhooks
- listing or revoking pairings
Use curl or the SDK for those. See the reference.
mcp install mints a scoped token
meetily-pro mcp install registers an MCP server that authenticates with a scoped, per-client token (Read plus Record by default; add --write for write access), not the loopback token. The in-app Integrations panel is an alternative that can additionally grant Delete. See Limitations and roadmap.
Last updated on
