mcloud-organizations — Claude Code skill: Medusa Cloud orgs
This skill lets your agent run mcloud organizations commands: list Cloud organizations, resolve an ID by name, pull subscription and member details.
npx skills add medusajs/medusa-agent-skills --skill mcloud-organizations -a claude-codeWhat mcloud-organizations does
The skill wires mcloud organizations into your agent. It can list every organization the account can reach, resolve an organization ID from its display name, or fetch a full record: metadata, subscription, members with roles and emails.
Two commands are covered, plus a breakdown of the JSON fields. organizations list needs personal auth — browser login or a personal access key. An organization access key returns 401 on that command. If you are authenticated through MCLOUD_TOKEN with an org key, get the organization ID from mcloud whoami --json instead. Worth knowing before the first run, otherwise the agent hits the error and starts guessing.
Only three command groups are allowed: mcloud organizations*, mcloud use* and jq*. The last one matters because most useful output is piped through jq — member emails, plan name, active flag. Install goes through npx skills add with the target agent flag.
What it helps with
- list the organizations an account can access
- resolve an organization ID from its name
- read member emails and roles
- check the current plan and whether the subscription is active
- switch the active context to a specific organization
Example prompts for the agent
- List all organizations my account has access to
- Find the ID of the organization named My Organization
- Show me the email of every member in org_123
How to install mcloud-organizations
1Skills CLI (Vercel)
npx skills add medusajs/medusa-agent-skills --skill mcloud-organizations -a claude-code2Manually: put the files in place
~/.claude/skills/mcloud-organizations/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/mcloud-organizations/
1Skills CLI (Vercel)
npx skills add medusajs/medusa-agent-skills --skill mcloud-organizations -a codex2Manually: put the files in place
.agents/skills/mcloud-organizations/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add medusajs/medusa-agent-skills --skill mcloud-organizations -a cursor2Manually: put the files in place
.cursor/skills/mcloud-organizations/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install medusajs/medusa-agent-skills mcloud-organizations2Manually: put the files in place
.github/skills/mcloud-organizations/SKILL.md1Skills CLI (Vercel)
npx skills add medusajs/medusa-agent-skills --skill mcloud-organizations -a gemini-cli2Platform CLI
gemini skills install https://github.com/medusajs/medusa-agent-skills --path plugins/medusa-cloud/skills/mcloud-organizationsManually: put the files in place
.devin/skills/mcloud-organizations/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add medusajs/medusa-agent-skills --skill mcloud-organizations -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about mcloud-organizations
How do I install mcloud-organizations in Claude?
Run npx skills add medusajs/medusa-agent-skills --skill mcloud-organizations -a claude-code. The skill file lands at ~/.claude/skills/mcloud-organizations/SKILL.md.
What does mcloud-organizations do?
It teaches the agent to call mcloud organizations list and mcloud organizations get, parse the JSON, and pull out IDs, subscription data and members.
Why does organizations list return 401?
That command requires personal auth — browser login or a personal access key. An organization access key will not work; use mcloud whoami --json to get the organization ID in that case.
