Deploying your app

Ship to production from the IDE button or the CLI, add custom domains, read logs, and verify with the project’s own checks.

Ship it

The IDE’s Deploy button and the CLI run the same pipeline: build, checks, ship, health verification. From the terminal:

npx mlcl login                            # once
npx mlcl deploy --project <id> --follow   # watch it through
npx mlcl deploy status --project <id>     # (also: list / cancel)

Tip

CI, not a human, should run deploys: npx mlcl deploy workflow-github --project <id> (or workflow-gitlab) writes a ready-made workflow — --apply to commit it.

Custom domains

npx mlcl domain add app.example.com --project <id>
npx mlcl domain verify app.example.com --project <id>
npx mlcl domain list --project <id>

add prints the DNS records to set; verify confirms them and issues the certificate.

Logs and checks

npx mlcl logs --project <id> --stream
npx mlcl check --project <id>             # typecheck, lint, build, unit, e2e

check discovers the project’s own scripts and runs them concurrently, printing one compact report with the first actionable error of each failed step. The same verification is available to agents as the check_project MCP tool.

Snapshots, staging, egress

Snapshots — npx mlcl snapshot create/list/restore/rm --project <id>: point-in-time copies of the sandbox you can roll back to.
Per-branch staging — npx mlcl stage up (with down / status / logs).
Outbound egress — sandbox network calls are allowlisted by default; approve a host with npx mlcl egress approve <host> --project <id>.