env check knows what your app needs from the code and the installed packages; set, sync, and manage secrets from the CLI.
env check cross-references what the code reads and what the installed packages declare against your .env files, and reports each missing variable with how to get its value:
mlcl env check
mlcl env check --fix # append the fixable ones for youmlcl env list --raw # the local .env, unmasked
mlcl env set KEY=VALUE # create or update
mlcl env get KEY # script-friendly
mlcl env unset KEY # comment out; value preservedmlcl env push --project <id> # local .env → the project
mlcl env pull --project <id> # project → local (write-only secrets skipped)
mlcl env detected --project <id> # what the deployed code + packages expectFor secrets you don’t want in files at all, the vault stores them server-side; project API keys (mk_…) let an app you host elsewhere call the molecule broker:
mlcl vault set STRIPE_KEY <value> --project <id> # (also: list / rm / token / broker)
mlcl apikey create --name ci --project <id> # (also: list / rm)To drive the platform itself from CI or a script (deploys, projects, the CLI), use a personal API token instead.