--- name: Mcloud Variables slug: mcloud-variables category: DevOps description: Mcloud Variables executes mcloud variables commands to list, read, set, and delete environment variables in a Cloud environment. Use it when inspecting or changing runtime or build variables; do not use --reveal unless secret values are explicitly requested. github: "https://github.com/medusajs/medusa-agent-skills/tree/main/plugins/medusa-cloud/skills/mcloud-variables" language: JavaScript stars: 212 forks: 26 install: "npx degit https://github.com/medusajs/medusa-agent-skills/tree/main/plugins/medusa-cloud/skills/mcloud-variables ~/.claude/skills/mcloud-variables" installs_to: ~/.claude/skills/mcloud-variables source_path: plugins/medusa-cloud/skills/mcloud-variables/SKILL.md collection_size: 18 category_size: 920 collection_url: "https://dirskills.com/collections/medusajs/medusa-agent-skills" added: 2026-09-04T05:26:10.132Z last_synced: 2026-09-04T05:26:10.132Z canonical_url: "https://dirskills.com/skills/mcloud-variables" --- # Mcloud Variables Mcloud Variables executes mcloud variables commands to list, read, set, and delete environment variables in a Cloud environment. Use it when inspecting or changing runtime or build variables; do not use --reveal unless secret values are explicitly requested. **Install:** ```bash npx degit https://github.com/medusajs/medusa-agent-skills/tree/main/plugins/medusa-cloud/skills/mcloud-variables ~/.claude/skills/mcloud-variables ``` ## README # Cloud CLI: Variables Commands Execute `mcloud variables` commands to inspect and manage environment variables for Cloud environments. ## Constraints - **Never pass `--reveal` unless the user explicitly asks.** Secret values appear in terminal scrollback, log aggregators, and process listings. - **Variable changes need a deploy to apply.** `set`/`delete` don't rebuild or redeploy. Run `mcloud environments redeploy ` for a **runtime** variable, or `mcloud environments trigger-build ` for a **build** variable (a redeploy reuses the existing image and won't pick up build-variable changes). - **System variables can't be deleted**, and `delete` requires `--yes` in non-interactive mode. - Looking up or creating a variable by key requires `--project` and `--environment` (or the equivalent in active context). Referencing by ID (`var_...`) works without project/environment context. - `set` and `delete` require mcloud CLI v0.1.10+. ## Commands ### variables list List all environment variables for a Cloud environment. ```bash mcloud variables list \ --organization \ --project \ --environment \ --json ``` **Options:** - `-o/--organization ` — Organization ID (falls back to active context) - `-p/--project ` — Project ID or handle (falls back to active context) - `-e/--environment ` — Environment handle (falls back to active context) - `-t/--type ` — Which variable set to list (default: `backend`) - `--scope ` — Filter by scope; repeatable (default: both scopes) - `--include-system` — Include system variables Medusa auto-injects (default: `false`) - `--reveal` — Print secret values in plaintext instead of masking (**use only when explicitly asked**) - `--dotenv` — Output `.env`-formatted `KEY=VALUE` lines instead of a table - `--json` — Output as JSON ### variables get Retrieve a single variable by its ID (`var_...`) or key. ```bash # By key (requires project + environment context) mcloud variables get ADMIN_CORS \ --organization \ --project \ --environment \ --json # By ID (works without project/environment context) mcloud variables get var_01XYZ --json ``` **Arguments:** - `variable` — Variable ID (`var_...`) or key (required) **Options:** - `-o/--organization `, `-p/--project `, `-e/--environment ` - `-t/--type ` — Which variable set to read (default: `backend`) - `--reveal` — Print secret value in plaintext (**use only when explicitly asked**) - `--json` — Output as JSON ### variables set Create or update one or more variables. The CLI updates when you reference an existing key or a `var_...` ID, and creates otherwise. ```bash # Single variable mcloud variables set API_KEY pk_123 \ --organization \ --project \ --environment # Multiple at once mcloud variables set -v API_KEY=pk_123 -v CLIENT_ID=my_app # From a .env file mcloud variables set --env-file .env ``` **Arguments:** - `variable` — Variable ID (`var_...`) or key to set (omit when using `--var`/`--env-file`) - `value` — Value to set (required when a `variable` argument is passed) **Options:** - `-o/--organization `, `-p/--project `, `-e/--environment ` - `-t/--type ` — Which variable set to write (default: `backend`) - `-v/--var ` — A variable to set; repeatable - `--env-file ` — Set all variables from a `.env` file - `--secret`, `--no-secret` — Mark as secret (default: `false` for new variables) - `--build`, `--no-build` — Available at build time (default: `false` for new variables) - `--runtime`, `--no-runtime` — Available at runtime (default: `true` for new variables) - `--json` — Output as JSON > Redeploy (runtime) or trigger-build (build) afterward — see Constraints. ### variables delete Delete a variable by its ID (`var_...`) or key. **Irreversible; system variables can't be deleted.** ```bash mcloud variables delete API_KEY \ --organization \ --project \ --environment \ --yes ``` **Arguments:** - `variable` — Variable ID (`var_...`) or key to delete (required) **Options:** - `-o/--organization `, `-p/--project `, `-e/--environment ` - `-t/--type ` — Which variable set to delete from (default: `backend`) - `-y/--yes` — Skip confirmation prompt (required in non-interactive mode) - `--json` — Output as JSON ## Variable Fields (JSON) | Field | Description | |-------|-------------| | `id` | Variable ID (`var_...`) | | `key` | Variable name (e.g. `ADMIN_CORS`) | | `value` | Variable value (masked if `is_secret` and `--reveal` not passed) | | `is_secret` | Whether the variable is treated as a secret | | `is_build` | Available at build time | | `is_runtime` | Available at runtime | | `environment_id` | The environment ID this variable belongs to | | `source` | `user` for user-set variables, `system` for auto-injected ones | ## Examples ```bash # List all variables for the active environment mcloud variables list --json # List only runtime variables, including system ones mcloud variables list --scope runtime --include-system --json # List storefront variables mcloud variables list --type storefront --json # Get a variable by key (with active context) mcloud variables get DATABASE_URL --json # Get a variable by ID (no env context needed) mcloud variables get var_01XYZ --json # Set a single variable, then redeploy to apply (runtime) mcloud variables set REDIS_URL redis://cache:6379 mcloud environments redeploy production # Set a secret build-only variable, then trigger a build to apply mcloud variables set STRIPE_SECRET_KEY sk_live_123 --secret --build --no-runtime mcloud environments trigger-build production # Set multiple variables from a .env file mcloud variables set --env-file .env # Delete a variable (irreversible — confirm before running) mcloud variables delete OLD_FLAG --yes # Only reveal secrets when user explicitly asks mcloud variables get STRIPE_SECRET_KEY --reveal --json | jq -r '.value' # Export all variables to a .env file (user must explicitly request --reveal) mcloud variables list --reveal --dotenv > .env # Check if a specific variable exists mcloud variables list --json | jq '.[] | select(.key == "REDIS_URL")' ```