medusajs/medusa-agent-skills

mcloud-organizations

Execute mcloud organizations commands to list or get Cloud organizations.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/medusajs/medusa-agent-skills --skill mcloud-organizations

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

Cloud CLI: Organizations Commands

Execute mcloud organizations commands to list and retrieve Cloud organizations.

Constraints

  • organizations list requires personal auth (browser login or personal access key). Organization access keys return 401 on this command.
  • When authenticated with MCLOUD_TOKEN using an org access key, use mcloud whoami --json to get the organization ID instead.

Commands

organizations list

List all organizations your account has access to.

bash
mcloud organizations list --json

Options:

  • --json — Output as JSON

organizations get

Retrieve a single organization by ID. Returns metadata, subscription details, and members.

bash
mcloud organizations get <organization-id> --json

Arguments:

  • organization — Organization ID (required)

Options:

  • -o/--organization <id> — Override the organization in active context (must match the argument)
  • --json — Output as JSON

Organization Fields (JSON)

FieldDescription
idOrganization ID
nameOrganization display name
billing_emailBilling contact email
statusactive or otherwise
membersArray of member objects with id, role, user.email
subscriptionCurrent plan, period, and is_active flag
account_holderBilling account holder details

Examples

bash
# List all organizations
mcloud organizations list --json

# Set context to first organization
ORGANIZATION_ID=$(
  mcloud organizations list --json \
    | jq -r '.[0].id'
)
mcloud use --organization "$ORGANIZATION_ID"

# Find organization ID by name
ORGANIZATION_ID=$(
  mcloud organizations list --json \
    | jq -r '.[] | select(.name == "My Organization") | .id'
)

# Get organization details (subscription, members)
mcloud organizations get org_123 --json

# List member emails
mcloud organizations get org_123 --json \
  | jq -r '.members[].user.email'

# Check subscription plan
mcloud organizations get org_123 --json \
  | jq '{plan: .subscription.plan.name, status: .subscription.is_active}'

Tâches connexes

du même dépôt

Autres Skills

Tous les Skills
medusajs
Officiel

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.

Installations / 1h
2
GitHub Stars
237
Mis à jour
13 nov.
medusajs
Officiel

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,

Installations / 1h
2
GitHub Stars
234
Mis à jour
21 oct.
medusajs
Officiel

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.

Installations / 1h
1
GitHub Stars
234
Mis à jour
21 oct.
medusajs
Officiel

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

Installations / 1h
1
GitHub Stars
234
Mis à jour
21 oct.