---
title: "Cloud CLI v0.1.11: local builds, variable management, and more"
description: "Learn what's new in the Medusa Cloud CLI (mcloud): run local builds, manage environment variables with set and delete commands, and reference projects by name instead of ID."
url: https://medusajs.com/blog/medusa-cloud-cli-v0-1-11
last_updated: 2026-08-13T15:24:24Z
---

# Cloud CLI v0.1.11: local builds, variable management, and more

_Published 2026-07-27 by Pedro Guzmán in Product_

Medusa Cloud is the fastest, most reliable way to run Medusa applications, and we are continuously improving how it can be used by both agents and developers alike. Last week we released a new version of Medusa Cloud CLI (mcloud), v0.1.11. It adds three new capabilities:

1. Run builds of your Medusa Cloud project locally
2. Manage environment variables from the CLI
3. Support names when setting project and environment contexts.

Keep reading to learn more about these new features. Check out the [full changelog in the documentation](https://docs.medusajs.com/cloud/cli/changelog).

## Run Cloud builds locally

`mcloud local build` reproduces your Cloud build environment on your machine. It requires Docker to be installed and running. Run the command from the root of the repository you want to build.

The simplest usage builds the backend using settings inferred from your linked Cloud project:

```bash
mcloud local build

```

To build the storefront instead, pass `-t storefront`:

```bash
mcloud local build -t storefront

```

Cloud environment variables are pulled in automatically. You can override them by passing a local env file or individual values:

```bash
mcloud local build --env-file .env
mcloud local build -v NODE_ENV=production -v API_URL=http://localhost:9000

```

If you want to test a build for a repository that isn't deployed on Cloud yet, pass the path explicitly with `--root-path`:

```bash
mcloud local build --root-path ./my-new-backend

```

## Expanded variable management

Variable management now includes four commands: `list`, `get`, `set`, and `delete`. Previously, only `get` and `list` were available.

- `variables set` creates or updates environment variables. It accepts single assignments, batch operations via multiple `--var` flags, or `.env` file imports
- `variables delete` removes a variable by ID or key; the operation is irreversible and requires confirmation unless `--yes` is passed

```bash
mcloud variables set API_KEY pk_123

```

The `variables list` command now also supports `--reveal` to display masked secret values in plaintext, `--dotenv` to output in `.env` format, and `--include-system` to include auto-injected Medusa Cloud variables.

Changes to variables don't auto-deploy. Run `mcloud environments trigger-build` after updating or deleting variables to apply the changes.

```bash
mcloud environments trigger-build Production

```

## Reference context by name

Organization, project, and environment flags now accept names in addition to IDs/handles. Instead of:

```bash
mcloud local build --organization org_12345abc --project m12345 --environment e12345

```

You can pass the names directly:

```bash
mcloud local build --organization "John's projects" --project Bookstore --environment Production

```

This works across all commands that accept `--organization`, `--project`, and `--environment` flags, including `mcloud use` to set the context for future commands:

```bash
mcloud use --organization "John's projects" --project Bookstore --environment Production

```

## Get started

Update to `mcloud` v0.1.10 or later to access the new features:

```bash
npm install @medusajs/mcloud -g

```

See the [local build reference](https://docs.medusajs.com/cloud/cli/commands/local) and [variables reference](https://docs.medusajs.com/cloud/cli/commands/variables) in the docs to learn more about these commands.