# 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.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 1400 installs · ★ 235
- Author: medusajs
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/medusajs/medusa-agent-skills/tree/HEAD/plugins/medusa-cloud/skills/using-medusa-cloud/SKILL.md
- Updated: 2026-10-21
- HTML: https://affpapa.org/en/nevibecode/skills/using-medusa-cloud

## What it does

The skill is an operational guide for agents touching Medusa Cloud infrastructure via `mcloud`. It ships with three reference files: `setup.md` for CLI install and auth, `debugging-deployments.md` for failure recipes and log analysis, `environments-and-variables.md` for environment lifecycle and variables. The agent loads the matching file before any multi-step workflow.

Deployment status routes the debugging. `build-failed` sends you to `mcloud deployments build-logs <id>`. `deployment-failed` means the runtime crashed after a good build, so read `mcloud logs --deployment <id>`. `timed-out` needs both, build logs first. A second table picks between `mcloud environments redeploy <env>` for environment-side fixes and `mcloud environments trigger-build <env>` when the source branch changed.

The constraints matter more than the recipes. `mcloud login`, `mcloud use` without flags, and `delete` without `--yes` all need a TTY, so they break in CI, Docker, or piped input. Variable changes do not apply on their own: after `variables set` or `variables delete` you still need a redeploy or a new build. Production environments cannot be deleted at all. And `--json` does not combine with `--follow`, so programmatic log ingestion wants bounded `--from`/`--to` windows instead.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add medusajs/medusa-agent-skills --skill using-medusa-cloud -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/using-medusa-cloud/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/using-medusa-cloud/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add medusajs/medusa-agent-skills --skill using-medusa-cloud -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/using-medusa-cloud/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add medusajs/medusa-agent-skills --skill using-medusa-cloud -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/using-medusa-cloud/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install medusajs/medusa-agent-skills using-medusa-cloud
```

2. **Manually: put the files in place**
- File: `.github/skills/using-medusa-cloud/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add medusajs/medusa-agent-skills --skill using-medusa-cloud -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/medusajs/medusa-agent-skills --path plugins/medusa-cloud/skills/using-medusa-cloud
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/using-medusa-cloud/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add medusajs/medusa-agent-skills --skill using-medusa-cloud -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/medusajs/medusa-agent-skills/tree/HEAD/plugins/medusa-cloud/skills/using-medusa-cloud/SKILL.md

## When to use it
- find out why a Medusa Cloud build failed
- switch context to the right organization and environment
- apply environment variables after editing them
- decide between redeploy and trigger-build
- reproduce a build-failed run locally with `mcloud local build`

## Example prompts
- check the build logs of the last deployment and tell me what broke
- deploy the current changes to production and report the status
- set this environment variable and restart the runtime

## Similar
- [containerize-application](https://affpapa.org/en/nevibecode/commands/containerize-application.md) — command · 1200 installs
- [webflow-cli:cloud](https://affpapa.org/en/nevibecode/skills/webflow-clicloud.md) — skill · 1000 installs
- [cloud-build-basics](https://affpapa.org/en/nevibecode/skills/cloud-build-basics.md) — skill · 3900 installs
- [sasjs-cli](https://affpapa.org/en/nevibecode/skills/sasjs-cli.md) — skill · 1000 installs
- [convex-deploy-guard](https://affpapa.org/en/nevibecode/skills/convex-deploy-guard.md) — skill · 36000 installs
- [huawei-cloud-cci-instance-management](https://affpapa.org/en/nevibecode/skills/huawei-cloud-cci-instance-management.md) — skill · 16900 installs

From the same set: [medusajs/medusa-agent-skills](https://affpapa.org/en/nevibecode/by/medusajs/medusa-agent-skills.md) — 11 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md