Mcloud Auth
Execute mcloud authentication and context commands: login, logout, whoami, use, version, and signup. Use when setting up the CLI, switching accounts, verifying auth state, setting the active org/project/environment context, or checking the CLI version.
Install
/plugin marketplace add medusajs/medusa-agent-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add medusajs/medusa-agent-skills --skill mcloud-authgit clone --depth 1 https://github.com/medusajs/medusa-agent-skills.git /tmp/medusa-agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/medusa-agent-skills/plugins/medusa-cloud/skills/mcloud-auth ~/.claude/skills/mcloud-authPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Cloud CLI: Auth and Context Commands Execute authentication and context commands for the Medusa Cloud CLI. ## Constraints - `mcloud login`, `mcloud signup`, and `mcloud use` (without flags) require a **TTY** — they fail in CI, Docker, or piped input. Use `MCLOUD_TOKEN` or pass flags explicitly instead. - When `MCLOUD_TOKEN` is set, file-based credentials are ignored and `mcloud login` is rejected. Unset it to switch accounts. - Always verify auth before any state-changing command: `mcloud whoami --json | jq -e '.auth.kind != "none"'` ## Commands ### whoami Show authenticated user, auth method, and active context (organization, project, environment). ```bash mcloud whoami --json ``` **Options:** - `--json` — Output as JSON **Use to verify auth and scope:** ```bash mcloud whoami --json | jq -e '.auth.kind != "none" and .organization.id != null' ``` Exit code `0` = authenticated and scoped. Non-zero = stop and prompt the user. ### use Set the active organization, project, and/or environment so subsequent commands skip those flags. ```bash mcloud use \ --organization <org-id> \ --project <project-id-or-handle> \ --environment <environment-handle> ``` **CRITICAL:** `mcloud use` without flags is interactive and fails in CI/Docker/piped input. Always pass flags explicitly. **Options:** - `-o/--organization <id>` — Set active organization - `-p/--project <id-or-handle>` — Set active project - `-e/--environment <handle>` — Set active environment
Details
- Skill name
mcloud-auth- Repository
- medusajs/medusa-agent-skills
- Path
plugins/medusa-cloud/skills/mcloud-auth/SKILL.md- Repo updated
- 13 November 2026
FAQ
What does the Mcloud Auth skill do?
Execute mcloud authentication and context commands: login, logout, whoami, use, version, and signup. Use when setting up the CLI, switching accounts, verifying auth state, setting the active org/project/environment context, or checking the CLI version.
How do I install the Mcloud Auth skill?
Claude Code plugin: /plugin marketplace add medusajs/medusa-agent-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Mcloud Auth popular?
It lives in medusajs/medusa-agent-skills, which has 237 GitHub stars and 29 forks.
Related skills
Building Admin Dashboard Customizations
237medusajs/medusa-agent-skills
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.
Building Storefronts
237medusajs/medusa-agent-skills
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.
Building with Medusa
237medusajs/medusa-agent-skills
Load automatically when planning, researching, or implementing ANY Medusa backend features (custom modules, API routes, workflows, data models, module links, business logic). REQUIRED for all Medusa backend work in ALL modes (planning, implementation, exploration). Contains architectural patterns, best practices, and critical rules that MCP servers don't provide.
Moonbit Js Binding
423mizchi/skills
Write MoonBit bindings to JavaScript with `extern "js"`. Use for FFI declarations against browser/Node/Deno APIs or npm packages, wrapping JS objects in opaque types, bridging Promises (`async fn` / `Promise::wait()`), `moon.pkg` exports (esm/cjs/iife), and null/undefined at the JS boundary.
Moonbit Practice
423mizchi/skills
MoonBit code generation and packaging best practices. Use when writing MoonBit code to avoid common AI mistakes with syntax, tests, and benchmarks, or when defining and publishing a Wasm executable with SKILL.md for the MoonBit Skills Marketplace.
Skill Forge Evolve
189AgriciDaniel/skill-forge
Improve and iterate on existing Claude Code skills based on usage feedback, test results, or changing requirements. Handles under/over-triggering fixes, instruction refinement, new sub-skill addition, and architecture evolution. Use when user says "improve skill", "fix skill", "skill not triggering", "skill triggers too much", "update skill", or "evolve skill".
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.