Mcloud Deployments

This wraps the mcloud CLI's deployment inspection commands so Claude can check build status, list recent deploys, and pull build logs when things break. You'd reach for it when debugging failed builds or tracking down which commit went live in which environment. It enforces JSON output for reliable parsing and reminds Claude to confirm org and project context before running commands. The build logs command is the real workhorse here since it's your first stop when a deployment shows build-failed status. Works with both deployment IDs and build IDs, and handles filtering by environment, commit SHA, or deployment type.

skills.sh installs: 1.5K
GitHub stars: 236
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add medusajs/medusa-agent-skills --skill mcloud-deployments --agent claude-code

Installs into .claude/skills of the current project.

Files

Cloud CLI: Deployments Commands

Execute mcloud deployments commands to inspect deployments and their build logs.

Constraints

Always pass --json when parsing output — plaintext format may change.
Always confirm context (mcloud whoami --json) before running commands if org/project are not already known.
Use --deployment IDs in the format depl_* 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> --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)
-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