Terminal
Terminal/Skill
Manages Medusa Cloud environments: list, inspect, create, delete, redeploy, and start builds from source.
By Medusa
Works with
npx skills add medusajs/medusa-agent-skills --skill mcloud-environmentsExecute mcloud environments commands to manage environment lifecycle and deployments.
type via environments get --json before attempting delete in automation.--yes for destructive operations (delete) in non-interactive contexts.redeploy vs trigger-build are not interchangeable — choose the right one based on where the fix is.List all environments in a project.
mcloud environments list --organization <org-id> --project <project-id-or-handle> --json
Options:
-o/--organization <id> — Organization ID (falls back to active context)-p/--project <id-or-handle> — Project ID or handle (falls back to active context)--json — Output as JSONRetrieve a single environment by its ID or handle.
mcloud environments get <environment-id-or-handle> --organization <org-id> --project <project-id-or-handle> --json
Arguments:
environment — Environment ID or handle (required)Options:
-o/--organization <id>, -p/--project <id-or-handle>, --jsonCreate a new long-lived environment.
mcloud environments create \
--organization <org-id> \
--project <project-id-or-handle> \
--name "Staging" \
--branch develop \
--json
Options:
-o/--organization <id>, -p/--project <id-or-handle>-n/--name <name> — Environment name (required)-b/--branch <branch> — Git branch to track (required)--custom-subdomain <subdomain> — Optional custom subdomain--json — Output as JSONDelete an environment. Cannot delete production environments.
mcloud environments delete <environment-id-or-handle> \
--organization <org-id> \
--project <project-id-or-handle> \
--yes
Arguments:
environment — Environment ID or handle (required)Options:
-o/--organization <id>, -p/--project <id-or-handle>-y/--yes — Skip confirmation prompt (required in non-interactive mode)--json — Output as JSONRe-run an existing build for the active deployment. Use when the fix is environment-side (variable change, infra issue) — does NOT start a new build.
mcloud environments redeploy <environment-id-or-handle> \
--organization <org-id> \
--project <project-id-or-handle> \
--json
Arguments:
environment — Environment ID or handle (required)Options:
-o/--organization <id>, -p/--project <id-or-handle>, --jsonRequires the environment to have an active deployment. If it doesn't, use
trigger-buildfirst.
Start a new build from the tracked branch. Use when the fix is committed code — creates a new deployment.
mcloud environments trigger-build <environment-id-or-handle> \
--organization <org-id> \
--project <project-id-or-handle> \
--json
Arguments:
environment — Environment ID or handle (required)Options:
-o/--organization <id>, -p/--project <id-or-handle>, --json| Command | When to use |
|---|---|
redeploy | Fix is environment-side (variable change, infra config) — reruns existing build |
trigger-build | Fix is in source code on the tracked branch — starts a new build |
# List all environments
mcloud environments list --json
# Get environment details and check type before deleting
mcloud environments get staging --json | jq '{id, name, type, status}'
# Create a new environment tracking the develop branch
mcloud environments create --name "Staging" --branch develop --json
# Delete a non-production environment
mcloud environments delete staging --yes
# Redeploy after a variable change
mcloud environments redeploy production --json
# Trigger a fresh build from source
mcloud environments trigger-build production --json
# Find environment handles by name
mcloud environments list --json \
| jq -r '.[] | select(.name == "Production") | .handle'
# Verify new build started
mcloud deployments list --environment production --limit 5 --json \
| jq '.[] | {id, backend_status, updated_at}'