Overview
The DCD CLI is the primary way to interact with DeviceCloud from your terminal or CI/CD pipeline. It is a drop-in replacement for maestro cloud — in most cases you can swap maestro cloud for dcd cloud.
The CLI is published as @devicecloud.dev/dcd on npm and as a standalone binary. The same package also ships an MCP server so AI agents can drive DeviceCloud directly.
Installation
The recommended install is the standalone binary — it has no dependencies and doesn't require Node.
curl -fsSL https://get.devicecloud.dev/install.sh | shirm https://get.devicecloud.dev/install.ps1 | iexRequires Node 22 or newer.
npm install -g @devicecloud.dev/dcdIn CI, you can skip a separate install step and run the CLI directly with npx:
npx --yes @devicecloud.dev/dcd@latest cloud <app-file> <flows-dir>Upgrading
If you installed the standalone binary, update it in place:
dcd upgradeIf you installed via npm, upgrade with npm instead:
npm install -g @devicecloud.dev/dcd@latestAuthentication
There are two ways to authenticate. See Authentication for full detail.
dcd login(recommended for local use) — authenticate once in your browser. The CLI stores a session, so you don't have to pass a key on every command, and it unlocks live test updates.API key (recommended for CI/headless) — set the
DEVICE_CLOUD_API_KEYenvironment variable, or pass--api-key <key>on any command.
When both are present, precedence is: --api-key flag → DEVICE_CLOUD_API_KEY env var → stored dcd login session.
Commands
Upload an app and run Maestro flows on DeviceCloud
Upload an app binary and get a reusable binary ID
Check the status of a test upload
List recent uploads for your organisation
Download artifacts or reports for a completed run
Authenticate via your browser
Clear the stored session
Show the logged-in user and active organisation
Switch the active organisation
Start and interact with a live device session (beta)
dcd upgrade
Upgrade the standalone binary in place
Getting Help
Last updated