Mcloud Deployments
- 685 installs
- 207 repo stars
- Updated July 31, 2026
- medusajs/medusa-agent-skills
mcloud-deployments is a Claude Code agent skill that runs Medusa Cloud `mcloud deployments` CLI commands with JSON parsing so developers can list deployments, inspect status, and fetch build logs during Medusa storefront
About
mcloud-deployments is a Medusa agent skill from medusajs/medusa-agent-skills that wraps the Medusa Cloud CLI for deployment inspection and promotion. The skill runs `mcloud deployments` commands with mandatory `--json` output, confirms org and project context via `mcloud whoami --json`, and uses `jq` to parse deployment records and build logs keyed by `depl_*` deployment IDs or build IDs. Developers reach for mcloud-deployments when they need repeatable rollout steps, environment targeting, or post-deploy verification on Medusa Cloud without manually chaining shell commands. The skill is constrained to Bash tools scoped to `mcloud deployments*` and `jq*`, making it suitable for agents debugging failed builds or checking release status on mcloud.
- Medusa Cloud deploy workflows
- Environment promotion steps
- Release verification checks
- Rollback-aware rollout guidance
- Ecommerce backend shipping
Mcloud Deployments by the numbers
- 685 all-time installs (skills.sh)
- +73 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #222 of 1,435 DevOps & CI/CD skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/medusajs/medusa-agent-skills --skill mcloud-deploymentsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 685 |
|---|---|
| repo stars | ★ 207 |
| Last updated | July 31, 2026 |
| Repository | medusajs/medusa-agent-skills ↗ |
How do you inspect Medusa Cloud deployment status and build logs?
Deploy and promote Medusa Cloud storefront/backend releases when you need repeatable rollout steps, environment targeting, and post-deploy verification on mcloud.
Who is it for?
Developers operating Medusa Cloud storefront or backend releases who already use the mcloud CLI and need agent-driven deployment listing, status checks, and build log retrieval.
Skip if: Teams not on Medusa Cloud or developers who need local Docker builds, CI pipeline authoring, or non-Medusa deployment platforms.
When should I use this skill?
The user asks to list mcloud deployments, check Medusa Cloud deployment status, promote a release, or debug a failed mcloud build using deployment or build IDs.
What you get
Parsed JSON deployment lists, deployment detail records, and build log output for Medusa Cloud `depl_*` releases.
- Deployment status JSON
- Build log output
- Deployment detail records
Files
Cloud CLI: Deployments Commands
Execute mcloud deployments commands to inspect deployments and their build logs.
Constraints
- Always pass
--jsonwhen parsing output — plaintext format may change. - Always confirm context (
mcloud whoami --json) before running commands if org/project are not already known. - Use
--deploymentIDs in the formatdepl_*or build IDs; build IDs resolve to their latest deployment automatically.
Commands
deployments list
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 JSON
deployments get
Retrieve 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>,--json
deployments build-logs
Fetch 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
Deployment Statuses
| 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 |
Examples
# 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 bld_01ABC123
# Read storefront build logs
mcloud deployments build-logs bld_01ABC123 --type storefront
# Filter deployments by commit SHA
mcloud deployments list --commit a1b2c3d --json | jq '.'
# Get deployments for a specific environment
mcloud deployments list --environment production --jsonRelated skills
Azure DeploySafely execute production deployments of already-prepared applications to Microsoft Azure.485k1.3kAzure ValidateRun deep pre-deployment checks on Azure configuration, infrastructure definitions, RBAC roles, and managed identities before pushing to production.485k1.3k
Github Actions DocsGet precise, docs-grounded answers about GitHub Actions workflows, syntax, security, and migration instead of relying on stale knowledge.275k72
Setup Pre CommitAutomatically run Prettier, type checking, and tests on every commit via Husky and lint-staged.170k199k
Deploy To VercelSafely turn any local project into a live Vercel preview with one instruction.99.3k29.7kVercel Cli With TokensDeploy projects to Vercel from agents and scripts using token authentication instead of interactive browser login.74.6k29.7kHow it compares
Choose mcloud-deployments over generic DevOps skills when the target is Medusa Cloud specifically and you need JSON-scoped `mcloud deployments` inspection rather than broad CI/CD pipeline design.
FAQ
What CLI does mcloud-deployments use?
mcloud-deployments runs Medusa Cloud `mcloud deployments` commands with the `--json` flag and parses output using `jq`. The skill confirms context first with `mcloud whoami --json` when org or project is unknown.
Which deployment IDs does mcloud-deployments accept?
mcloud-deployments targets Medusa Cloud deployment IDs in the `depl_*` format or associated build IDs when listing deployments, retrieving details, or fetching build logs for debugging.
When should an agent invoke mcloud-deployments?
Invoke mcloud-deployments when a developer needs to list Medusa Cloud deployments, check rollout status, read build output, or debug a failed mcloud build during storefront or backend release promotion.