Skip to main content
The Tallwatch CLI is a thin client over the public REST API. Use it in CI, on your laptop, or to import monitors from UptimeRobot. The control plane stays on Tallwatch — the CLI only calls https://api.tallwatch.com.

Install

Requires Node.js 20+.
Or with npm:
Verify:

Sign in

Run tallwatch login with no flags. The CLI starts a device session, opens your browser, and polls until you approve.
  1. The terminal prints a one-time code and opens your browser.
  2. Sign in if needed — approval is automatic when the URL includes your code.
  3. Tallwatch creates an API key and delivers it to the CLI over the short-lived device session.
  4. The browser tab can close. The terminal prints login success.
This works on SSH and remote machines: the browser can run on your laptop while the CLI runs on a server. Use --no-browser to print the URL yourself. The key is saved to ~/.config/tallwatch/config.json (mode 0600 on Unix). On Windows the path is %USERPROFILE%\.config\tallwatch\config.json.

Manual key

Paste a key directly:
Create keys in Settings → API keys, or run tallwatch login to authorize from the terminal.

Environment overrides

Use tallwatch login --no-browser when the CLI runs on a remote machine and you open the login URL on your laptop.

Commands

Same surface as the MCP server. Add --json on list, show, and mutating commands for scripting. List --limit max is 15. Examples:

UptimeRobot import

Export monitors from UptimeRobot, dry-run the mapping, then apply:
Dry-run works without login. --apply requires a signed-in CLI. HTTP (type 1) and keyword (type 2) monitors map to Tallwatch HTTP checks. Ping, port, and heartbeat exports are skipped with a reason.

Auth and limits

The CLI uses the same API keys and rate limits as curl or MCP. Keys need read to list; write to create, pause, or resolve. CLI login creates a key named CLI login with read + write scopes. Revoke it anytime from Settings. API keys. MCP server for AI agents. Install page: tallwatch.com/cli.