Setting the skill. One moment.
18 skills · 52 min
Medusa Cloud
Skill 4 of 18
Execute mcloud deployments commands to list deployments, retrieve deployment details, and fetch build logs.
1 minute · 200 words · 8 sections
Install
npx skills add medusajs/medusa-agent-skills --skill mcloud-deploymentsnpx skills add medusajs/medusa-agent-skills/plugin marketplace add medusajs/medusa-agent-skillsThe first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.
Execute mcloud deployments commands to inspect deployments and their build logs.
--json when parsing output — plaintext format may change.mcloud whoami --json) before running commands if org/project are not already known.--deployment IDs in the format depl_* or build IDs; build IDs resolve to their latest deployment automatically.List recent deployments for a project (default: 20 most recent across all environments).
mcloud deployments list --organization <org-id> --project <project-id-or-handle> --jsonOptions:
-o/--organization <id> — Organization ID (falls back to active context)-p/--project <id-or-handle> — Project ID or handle (falls back to active context)-e/--environment <handle> — Filter by environment handle--environment-type <production|long-lived|preview> — Filter by environment type--commit <sha> — Filter by Git commit SHA (full or prefix)--limit <1-200> — Max results (default: 20)--offset <number> — Pagination offset (default: 0)--json — Output as JSONRetrieve a single deployment’s details by ID.
mcloud deployments get <deployment-id> --organization <org-id> --project <project-id-or-handle> --jsonArguments:
deployment — Deployment ID (required)Options:
-o/--organization <id>, -p/--project <id-or-handle>, --jsonFetch build logs for a deployment. Use this to debug build-failed status.
mcloud deployments build-logs <deployment-id> --organization <org-id> --project <project-id-or-handle>Arguments:
deployment — Deployment ID (required)Options:
-o/--organization <id>, -p/--project <id-or-handle>--type <backend|storefront> — Which build log stream to read (default: backend)--json — Output as JSON| Status | Meaning |
|---|---|
created | Build not started yet |
building | Build running |
built | Build succeeded, awaiting rollout |
deploying | Rolling out to environment |
deployed | Live and serving traffic |
build-failed | Build step failed — read build-logs |
deployment-failed | Build succeeded, runtime crashed — read mcloud logs |
timed-out | Exceeded time budget (backend only) |
canceled | Superseded by a newer deployment |
idle | No longer the active deployment |
# List all deployments (with active context set)
mcloud deployments list --json
# Find most recent build-failed deployment
mcloud deployments list --json \
| jq -r '[.[] | select(.backend_status == "build-failed")][0].id'
# Get deployment details
mcloud deployments get bld_01ABC123 --json
# Read backend build logs
mcloud deployments build-logs
Execute mcloud deployments commands to list deployments, retrieve deployment details, and fetch build logs. Use when listing deployments, checking deployment status, or reading build output for debugging build failures.
The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.
Bash(mcloud deployments*)Bash(jq*)plugins/medusa-cloud/skills/mcloud-deployments/SKILL.mdmain, last pushed 22 September 2026.SKILL.md, not by matching a directory convention. 4 distinct layouts observed: plugins/ecommerce-storefront/skills/*/SKILL.md, plugins/learn-medusa/skills/*/SKILL.md, plugins/medusa-cloud/skills/*/SKILL.md, plugins/medusa-dev/skills/*/SKILL.md.h1 and no skipped levels:.claude-plugin/marketplace.json by Medusa, declaring 4 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree./medusajs/medusa-agent-skills.md, and each skill at its own .md URL.