/mcloud-projects
Execute mcloud projects commands to list, get, or delete Cloud projects. Use when discovering projects, resolving project handles by name, or retrieving project details including linked environments.
$ npx -y skills add medusajs/medusa-agent-skills --skill mcloud-projects --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/mcloud-projects
Context preview
The summary Claude sees to decide when to auto-load this skill.
Execute mcloud projects commands to list, get, or delete Cloud projects. Use when discovering projects, resolving project handles by name, or retrieving project details including linked environments.
SKILL.md
mcloud-projects.SKILL.mdname: mcloud-projects
description: Execute mcloud projects commands to list, get, or delete Cloud projects. Use when discovering projects, resolving project handles by name, or retrieving project details including linked environments.
allowed-tools: Bash(mcloud projects*), Bash(mcloud use*), Bash(jq*)
Cloud CLI: Projects Commands
Execute `mcloud projects` commands to manage Cloud projects.
Constraints
- `projects delete` is **irreversible** — removes all associated environments, deployments, and resources. Always confirm the project ID/handle before deleting.
- Use `--yes` with `delete` in non-interactive contexts (scripts, pipelines, agents).
Commands
projects list
List projects in an organization. If `--organization` is omitted (and no active context org is set), lists projects across all organizations you have access to, grouped by organization.
mcloud projects list --organization <org-id> --json
**Options:**
- `-o/--organization <id>` — Organization ID (falls back to active context; if unset, lists across all your organizations)
- `--json` — Output as JSON
projects get
Retrieve a single project by its ID or handle.
mcloud projects get <project-id-or-handle> --organization <org-id> --json
**Arguments:**
- `project` — Project ID or handle (required)
**Options:**
- `-o/--organization <id>` — Organization ID (falls back to active context; **required**)
- `--json` — Output as JSON
projects delete
Delete a project by its ID or handle. **Irreversible.**
mcloud projects delete <project-id-or-handle> \
--organization <org-id> \
--yes
**Arguments:**
- `project` — Project ID or handle (required)
**Options:**
- `-o/--organization <id>` — Organization ID (falls back to active context; **required**)
- `-y/--yes` — Skip confirmation prompt (required in non-interactive mode)
- `--json` — Output as JSON
Project Fields (JSON)
| Field | Description | |-------|-------------| | `id` | Project ID | | `handle` | URL-safe project handle (used in most commands) | | `name` | Display name | | `status` | `ready` when healthy | | `region` | Deployment region (e.g. `us-east-1`) | | `repository` | Linked GitHub repository (`owner/repo`) | | `root_path` | Root path within the repository | | `organization` | Owning organization (`id`, `name`, `created_at`) | | `environments` | Array of associated environments (each may include `storefront_environments`) |
Examples
# List all projects in an organization
mcloud projects list --organization org_123 --json
# Set context to a project by name
PROJECT_HANDLE=$(
mcloud projects list --organization org_123 --json \
| jq -r '.[] | select(.name == "My Store") | .handle'
)
mcloud use --project "$PROJECT_HANDLE"
# Get project details including environments
mcloud projects get my-store --organization org_123 --json
# List all environment handles for a project
mcloud projects get my-store --organization org_123 --json \
| jq -r '.environments[].handle'
# Find project handle by name
mcloud projects list --organization org_123 --json \
| jq -r '.[] | select(.name == "My Store") | .handle'
# Delete a project (irreversible — confirm before running)
mcloud projects delete old-project --organization org_123 --yesRead more
name: mcloud-projects description: Execute mcloud projects commands to list, get, or delete Cloud projects. Use when discovering projects, resolving project handles by name, or retrieving project details including linked environments. allowed-tools: Bash(mcloud projects*), Bash(mcloud use*), Bash(jq*)
Cloud CLI: Projects Commands
Execute `mcloud projects` commands to manage Cloud projects.
Constraints
- `projects delete` is **irreversible** — removes all associated environments, deployments, and resources. Always confirm the project ID/handle before deleting.
- Use `--yes` with `delete` in non-interactive contexts (scripts, pipelines, agents).
Commands
projects list
List projects in an organization. If `--organization` is omitted (and no active context org is set), lists projects across all organizations you have access to, grouped by organization.
mcloud projects list --organization <org-id> --json
**Options:**
- `-o/--organization <id>` — Organization ID (falls back to active context; if unset, lists across all your organizations)
- `--json` — Output as JSON
projects get
Retrieve a single project by its ID or handle.
mcloud projects get <project-id-or-handle> --organization <org-id> --json
**Arguments:**
- `project` — Project ID or handle (required)
**Options:**
- `-o/--organization <id>` — Organization ID (falls back to active context; **required**)
- `--json` — Output as JSON
projects delete
Delete a project by its ID or handle. **Irreversible.**
mcloud projects delete <project-id-or-handle> \ --organization <org-id> \ --yes
**Arguments:**
- `project` — Project ID or handle (required)
**Options:**
- `-o/--organization <id>` — Organization ID (falls back to active context; **required**)
- `-y/--yes` — Skip confirmation prompt (required in non-interactive mode)
- `--json` — Output as JSON
Project Fields (JSON)
| Field | Description | |-------|-------------| | `id` | Project ID | | `handle` | URL-safe project handle (used in most commands) | | `name` | Display name | | `status` | `ready` when healthy | | `region` | Deployment region (e.g. `us-east-1`) | | `repository` | Linked GitHub repository (`owner/repo`) | | `root_path` | Root path within the repository | | `organization` | Owning organization (`id`, `name`, `created_at`) | | `environments` | Array of associated environments (each may include `storefront_environments`) |
Examples
# List all projects in an organization
mcloud projects list --organization org_123 --json
# Set context to a project by name
PROJECT_HANDLE=$(
mcloud projects list --organization org_123 --json \
| jq -r '.[] | select(.name == "My Store") | .handle'
)
mcloud use --project "$PROJECT_HANDLE"
# Get project details including environments
mcloud projects get my-store --organization org_123 --json
# List all environment handles for a project
mcloud projects get my-store --organization org_123 --json \
| jq -r '.environments[].handle'
# Find project handle by name
mcloud projects list --organization org_123 --json \
| jq -r '.[] | select(.name == "My Store") | .handle'
# Delete a project (irreversible — confirm before running)
mcloud projects delete old-project --organization org_123 --yesA collection of skills composed as Claude Code plugins for building Medusa applications with best practices and architectural patterns. These skills can be used with any agent, as explained in the Usage with Other Agents section.
Repo: medusajs/medusa-agent-skills
Other skills on medusa-agent-skills.
- /storefront-best-practices
ALWAYS use this skill when working on ecommerce storefronts, online stores, shopping sites. Use for ANY storefront component including checkout pages, cart, payment flows, product pages, product listings, navigation, homepage, or ANY page/component in a storefront. CRITICAL for
Open skill - /learning-medusa
Load automatically when user asks to learn Medusa development (e.g., "teach me how to build with medusa", "guide me through medusa", "I want to learn medusa"). Interactive guided tutorial where Claude acts as a coding bootcamp instructor, teaching step-by-step with checkpoints
Open skill - /mcloud-auth
Execute mcloud authentication and context commands: login, logout, whoami, use, version, and signup. Use when setting up the CLI, switching accounts, verifying auth state, setting the active org/project/environment context, or checking the CLI version.
Open skill - /mcloud-deployments
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.
Open skill - /mcloud-environments
Execute mcloud environments commands to list, get, create, delete, redeploy, or trigger builds for Cloud environments. Use when managing environment lifecycle, redeploying after variable changes, or starting new builds from source.
Open skill - /mcloud-local
Execute mcloud local build to reproduce a Cloud build on the local machine. Use when debugging a build-failed deployment without pushing to the tracked branch, iterating on a build fix, or testing build-variable changes locally. Requires Docker and must run inside the project's
Open skill

