Mcloud Projects
- 669 installs
- 207 repo stars
- Updated July 31, 2026
- medusajs/medusa-agent-skills
mcloud-projects is a Claude Code skill that runs Medusa Cloud CLI project commands so developers who host Medusa stores can list, inspect, switch, and delete cloud projects from an agent session.
About
mcloud-projects is an agent skill for Medusa Cloud that wraps Bash access to mcloud projects and mcloud use, plus jq for parsing JSON output. Developers invoke it when onboarding new stores, resolving project handles by name, retrieving linked environment details, or cleaning up obsolete hosted commerce projects. The skill documents irreversible delete behavior and recommends --yes for scripted or non-interactive deletes. Allowed tools are scoped to mcloud projects*, mcloud use*, and jq*, keeping agent actions aligned with official Medusa Cloud project management workflows rather than ad-hoc API calls.
- Project provisioning on mcloud
- Repo and service linkage
- Multi-environment organization
- Commerce workspace setup
- Hosted project governance
Mcloud Projects by the numbers
- 669 all-time installs (skills.sh)
- +74 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #341 of 1,039 Cloud & Infrastructure 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-projectsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 669 |
|---|---|
| repo stars | ★ 207 |
| Last updated | July 31, 2026 |
| Repository | medusajs/medusa-agent-skills ↗ |
How do you list Medusa Cloud projects from CLI?
Create, list, and configure Medusa Cloud projects when onboarding new stores, linking repos, or reorganizing hosted commerce environments across teams.
Who is it for?
Backend developers operating Medusa Cloud-hosted stores who need repeatable project discovery and context switching from Claude Code or Cursor.
Skip if: Developers building local Medusa apps without Medusa Cloud or teams that manage infrastructure only through the web dashboard.
When should I use this skill?
User asks to list, inspect, switch, or delete Medusa Cloud projects or resolve a project handle by name.
What you get
Current Medusa Cloud project IDs, handles, environment links, and active project context after mcloud use.
- project listing output
- active project context
- confirmed delete execution
By the numbers
- Scopes Bash to three tool patterns: mcloud projects*, mcloud use*, and jq*
Files
Cloud CLI: Projects Commands
Execute mcloud projects commands to manage Cloud projects.
Constraints
projects deleteis irreversible — removes all associated environments, deployments, and resources. Always confirm the project ID/handle before deleting.- Use
--yeswithdeletein non-interactive contexts (scripts, pipelines, agents).
Commands
projects list
List all projects in an organization.
mcloud projects list --organization <org-id> --jsonOptions:
-o/--organization <id>— Organization ID (falls back to active context; required)--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> --jsonArguments:
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> \
--yesArguments:
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 |
environments | Array of associated 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 --yesRelated skills
Azure AiIntegrates Azure AI Content Safety, Document Intelligence, Speech, and Search services into Java-based agents and applications.495k1.4kAzure PrepareGenerate the exact Azure infrastructure files, Dockerfiles, and azure.yaml configuration needed before deploying any new or modernized application.494k1.4kAzure StorageConnect agents and applications to Azure Blob Storage, File Shares, Queues, Tables, and Data Lake without leaving the coding environment.494k1.4kAppinsights InstrumentationAutomatically instrument web applications running on Azure App Service with Application Insights for observability without manual configuration.493k1.4kAzure Resource LookupInstantly list, query, and discover any Azure resources across subscriptions without leaving the agent chat.493k1.4kAzure AigatewayConfigure Azure API Management as a secure, governed gateway for routing traffic to LLMs, MCP servers, and agent tools.493k1.4kHow it compares
Choose mcloud-projects over generic cloud CLI skills when work targets Medusa Cloud commerce project handles and linked store environments.
FAQ
What commands does mcloud-projects run?
mcloud-projects executes Medusa Cloud CLI project commands—mcloud projects list, get, and delete—plus mcloud use for switching the active project. jq is allowed for parsing JSON fields like handles and linked environments.
Is deleting a Medusa Cloud project reversible?
No. mcloud projects delete is irreversible and removes associated environments, deployments, and resources. mcloud-projects instructs agents to confirm the project ID or handle before delete and to pass --yes in non-interactive scripts.