medusajs/medusa-agent-skills

mcloud-projects

Execute mcloud projects commands to list, get, or delete Cloud projects.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/medusajs/medusa-agent-skills --skill mcloud-projects

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

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.

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

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

bash
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)

FieldDescription
idProject ID
handleURL-safe project handle (used in most commands)
nameDisplay name
statusready when healthy
regionDeployment region (e.g. us-east-1)
repositoryLinked GitHub repository (owner/repo)
root_pathRoot path within the repository
organizationOwning organization (id, name, created_at)
environmentsArray of associated environments (each may include storefront_environments)

Examples

bash
# 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 --yes

Related by task

from this repository

More skills

All skills
medusajs
Official

building-admin-dashboard-customizations

Load automatically when planning, researching, or implementing Medusa Admin dashboard UI (widgets, custom pages, forms, tables, data loading, navigation). REQUIRED for all admin UI work in ALL modes (planning, implementation, exploration). Contains design patterns, component usage, and data loading patterns that MCP servers don't provide.

1h installs
2
GitHub stars
237
Updated
Nov 13
medusajs
Official

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 adding checkout, implementing cart, integrating Medusa backend, making a store agent-friendly for AI shopping agents, or building any ecommerce functionality. Framework-agnostic (Next.js, SvelteKit, TanStack Start, React,

1h installs
2
GitHub stars
234
Updated
Oct 21
medusajs
Official

building-storefronts

Load automatically when planning, researching, or implementing Medusa storefront features (calling custom API routes, SDK integration, React Query patterns, data fetching). REQUIRED for all storefront development in ALL modes (planning, implementation, exploration). Contains SDK usage patterns, frontend integration, and critical rules for calling Medusa APIs.

1h installs
1
GitHub stars
234
Updated
Oct 21
medusajs
Official

creating-internal-agents

Use when building an internal admin-facing AI agent in a Medusa project. These agents are operated by merchants and store operators — not customers. Covers data models, module service, agent runtime (tools, system prompt, streamText), streaming API routes (NDJSON), and admin UI chat extensions. Load for any internal agent type: store operations assistant, product audit, cohort analysis, customer service tooling for support staff, etc. Do NOT use for customer-facing agents (storefront chatbots, b

1h installs
1
GitHub stars
234
Updated
Oct 21