Skip to main content
skill CX Codex

mcloud-local — Claude Code skill for local builds

Run a Medusa Cloud build on your machine with mcloud local build. Use the skill to investigate a failed build or test build-variable changes before pushing.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add medusajs/medusa-agent-skills --skill mcloud-local -a claude-code
Open on GitHub

What mcloud-local does

mcloud-local helps reproduce a Cloud build locally. It can identify a failed deployment, find its commit, and check out that revision in Git. The command reports progress as plain text, so use its exit status to tell whether the build passed; its output is not JSON.

Build the backend by default, or choose the storefront with --type storefront. Test a variable with --var KEY=VALUE, or supply a local file using --env-file .env. Docker caching starts disabled; --docker-cache turns it on. Docker must be installed and running, and the command must run from inside the project's Git repository. This skill covers build failures, not runtime failures; the instructions direct runtime debugging to mcloud logs --deployment <id>.

What it helps with

  • reproduce a failed Cloud build locally
  • build the backend or storefront
  • test a build-variable change without editing code
  • identify the step that caused a build to fail

Example prompts for the agent

  • Reproduce the failed deployment's build at its commit.
  • Build the storefront from apps/storefront with mcloud local build --type storefront --storefront-path apps/storefront.
  • Test the build with NODE_ENV=production using mcloud local build --var NODE_ENV=production.

How to install mcloud-local

1Skills CLI (Vercel)

npx skills add medusajs/medusa-agent-skills --skill mcloud-local -a claude-code

2Manually: put the files in place

~/.claude/skills/mcloud-local/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/mcloud-local/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about mcloud-local

How do I install mcloud-local in Claude Code?

Run npx skills add medusajs/medusa-agent-skills --skill mcloud-local -a claude-code. The skill file is at ~/.claude/skills/mcloud-local/SKILL.md.

What does mcloud-local do?

It runs a Medusa Cloud build on your machine with mcloud local build, helping you reproduce a build failure at the relevant commit.

What do I need to run mcloud-local?

Docker must be installed and running, and you must be inside the project's Git repository. The skill addresses build failures, not runtime failures.

Similar skills

All skills for DevOps and infrastructure →

From the same set14

learning-medusa An interactive tutoring skill that guides you through Medusa architecture step by step with hands-on checkpoints. CX Codex +1 3,400installs using-medusa-cloud A skill that teaches an agent to run Medusa Cloud through the mcloud CLI: deploys, failed builds, environments, variables. Useful for CI/CD work. CX Codex +1 1,400installs mcloud-organizations This skill lets your agent run mcloud organizations commands: list Cloud organizations, resolve an ID by name, pull subscription and member details. CX Codex +1 1,300installs mcloud-logs A skill that teaches your agent to read backend and storefront logs with mcloud logs, filter them by time or deployment, and pipe them to JSON. CX Codex +1 1,300installs mcloud-projects Runs Medusa Cloud CLI commands to inspect and delete projects. Useful when managing cloud deployments and switching active project handles. CX Codex +1 1,300installs mcloud-environments Manage mcloud environments from your agent: inspect, create, or remove them, then rerun a deployment or start a fresh build. Useful when changing environment settings or shipping committed code. CX Codex +1 1,300installs mcloud-variables An agent skill that drives mcloud variables for Medusa Cloud environments: list keys, read one, write, delete, export to .env. CX Codex +1 1,300installs mcloud-deployments Enables agents to query Medusa Cloud deployments and inspect build logs via CLI. Useful for tracking release progress and debugging failed builds directly in the terminal. CX Codex +1 1,300installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor