
Mcloud Organizations
- 668 installs
- 207 repo stars
- Updated July 31, 2026
- medusajs/medusa-agent-skills
mcloud-organizations is a Claude agent skill that executes mcloud organizations CLI commands to list Medusa Cloud organizations, resolve organization IDs by name, and retrieve member and subscription details for multi-st
About
mcloud-organizations is an agent skill from medusajs/medusa-agent-skills that wraps mcloud organizations CLI commands for Medusa Cloud account administration. Allowed tools include Bash on mcloud organizations*, mcloud use*, and jq* for JSON output parsing. Developers use it to discover organizations, resolve organization IDs by name, and retrieve details including members and subscription status before running environment commands. The skill documents an auth constraint: organizations list requires personal authentication via browser login or personal access key, and organization access keys return 401 on that command. When authenticated with MCLOUD_TOKEN using an org access key, developers must use alternative discovery paths documented in the skill. Output includes organization listings and JSON metadata for account scoping.
- Medusa Cloud organization setup and administration
- Multi-project tenancy for ecommerce teams
- Team and access scoping across mcloud resources
- Agent workflows for org-level cloud governance
- Project grouping under a single cloud account
Mcloud Organizations by the numbers
- 668 all-time installs (skills.sh)
- +73 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #342 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-organizationsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 668 |
|---|---|
| repo stars | ★ 207 |
| Last updated | July 31, 2026 |
| Repository | medusajs/medusa-agent-skills ↗ |
How do you list Medusa Cloud organizations from the CLI?
Create and administer Medusa Cloud organizations, team access, and project grouping so multiple ecommerce stores and environments stay correctly scoped under one cloud account.
Who is it for?
Developers administering Medusa Cloud accounts who need agent-assisted organization discovery and ID resolution before creating or managing ecommerce environments.
Skip if: Developers who already have a resolved organization ID and only need environment redeploys, or teams without mcloud CLI personal authentication configured.
When should I use this skill?
The user asks to list Medusa Cloud organizations, resolve an organization ID by name, or retrieve organization members and subscription details via mcloud CLI.
What you get
Medusa Cloud organization listings, resolved organization IDs by name, and JSON metadata including members and subscription status.
- Organization listings and IDs
- Member and subscription metadata JSON
By the numbers
- Allows 3 Bash tool patterns: mcloud organizations*, mcloud use*, and jq*
Files
Cloud CLI: Organizations Commands
Execute mcloud organizations commands to list and retrieve Cloud organizations.
Constraints
organizations listrequires personal auth (browser login or personal access key). Organization access keys return 401 on this command.- When authenticated with
MCLOUD_TOKENusing an org access key, usemcloud whoami --jsonto get the organization ID instead.
Commands
organizations list
List all organizations your account has access to.
mcloud organizations list --jsonOptions:
--json— Output as JSON
organizations get
Retrieve a single organization by ID. Returns metadata, subscription details, and members.
mcloud organizations get <organization-id> --jsonArguments:
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)
| Field | Description |
|---|---|
id | Organization ID |
name | Organization display name |
billing_email | Billing contact email |
status | active or otherwise |
members | Array of member objects with id, role, user.email |
subscription | Current plan, period, and is_active flag |
account_holder | Billing account holder details |
Examples
# 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}'Related skills
FAQ
What auth does mcloud-organizations list require?
mcloud-organizations list requires personal authentication via browser login or a personal access key. Organization access keys return 401 on organizations list, so agents must use personal auth or alternative discovery paths documented in the skill.
What details does mcloud-organizations retrieve?
mcloud-organizations retrieves Medusa Cloud organization listings, resolves IDs by name, and returns details including members and subscription status. Developers use this before scoping environment or deployment commands to the correct account.