Agent skill

Medusa Cloud CLI Authentication

by medusajs in medusajs/medusa-agent-skills

Runs the mcloud commands for logging in, checking who is authenticated, and choosing the active organization, project and environment.

No licenceAuto-check passedDevOps & Cloud

Install Medusa Cloud CLI Authentication

skills CLI
$ npx skills add medusajs/medusa-agent-skills --skill mcloud-auth -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install medusajs/medusa-agent-skills mcloud-auth --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/medusajs/medusa-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/medusa-cloud/skills/mcloud-auth .claude/skills/mcloud-auth && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
mcloud-auth
GitHub stars
225
Token cost
~1.1k tokens
SKILL.md length
283 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
None found

At a glance

Runs the mcloud commands for logging in, checking who is authenticated, and choosing the active organization, project and environment.

  • Setting up the Medusa Cloud CLI on a new machine
  • SKILL.md covers Constraints, Commands, Auth Methods and Examples
  • Calls jq; needs MCLOUD_TOKEN
  • Switching between Medusa Cloud accounts or organizations

What it does

The skill wraps six commands of the Medusa Cloud CLI: `login`, `logout`, `whoami`, `use`, `version` and `signup`. `whoami --json` reports the user, the auth method and the active context, and the skill pipes it through `jq` to confirm the session is authenticated and scoped before any command that changes state. `use` sets the active organization, project and environment with `-o`, `-p` and `-e`, or clears them with `--clear`.

Several commands need an interactive terminal. `login`, `signup` and `use` without flags fail in CI, Docker or piped input, so the skill points to the `MCLOUD_TOKEN` environment variable or explicit flags there. When `MCLOUD_TOKEN` is set, stored credentials are ignored and `login` is rejected until you unset it. Its tool permissions are limited to `mcloud whoami`, `use`, `version`, `logout` and `jq`.

When your agent uses it

  • Setting up the Medusa Cloud CLI on a new machine
  • Switching between Medusa Cloud accounts or organizations
  • Checking that a session is authenticated before a deploy or other state-changing command
  • Pointing later commands at a specific project and environment

Example prompts

  • “Check whether I am logged in to Medusa Cloud and show the active project.”
  • “Switch the mcloud context to the staging environment of our storefront project.”
  • “Log out of mcloud and clear the stored credentials.”
  • “We run in CI, so authenticate mcloud with the access key from MCLOUD_TOKEN.”

Requirements

  • The `mcloud` CLI
  • `jq`
  • A Medusa Cloud account or an access key in `MCLOUD_TOKEN`
  • Pre-approved tools (allowed-tools): Bash(mcloud whoami*), Bash(mcloud use*), Bash(mcloud version*), Bash(mcloud logout*), Bash(jq*)

What it can do on your machine

Read from SKILL.md and the folder at commit 066132d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(mcloud whoami*)
    • Bash(mcloud use*)
    • Bash(mcloud version*)
    • Bash(mcloud logout*)
    • Bash(jq*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • MCLOUD_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Medusa Cloud CLI Authentication loads about 1.1k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 283 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~66
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Without a licence we can't republish the file, so here is its outline and opening line. It has 283 words (~1,057 tokens).

“Execute authentication and context commands for the Medusa Cloud CLI.”

— opening of SKILL.md by medusajs
name
mcloud-auth
allowed-tools
Bash(mcloud whoami*), Bash(mcloud use*), Bash(mcloud version*), Bash(mcloud logout*), Bash(jq*)

Read the full SKILL.md on GitHub

Files

Just SKILL.md in plugins/medusa-cloud/skills/mcloud-auth of medusajs/medusa-agent-skills.

Open the folder on GitHubat commit 066132d

Compare with similar skills

Medusa Cloud CLI Authentication next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Medusa Cloud CLI Authentication compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Medusa Cloud CLI Authentication this skillmedusajs/medusa-agent-skills225—~1.1kAutomated safety check: PassNone
Medusa DevelopmentMindrally/skills267—~2.7kAutomated safety check: PassApache-2.0
Vercel Deploybytedance/deer-flow83k10 repos~797Automated safety check: PassMIT
Update V8 Versionopeninterpreter/openinterpreter69k2 repos~845Automated safety check: PassApache-2.0
Analyze GitHub Action Logswithastro/astro63k1 repos~1.3kAutomated safety check: PassCustom licence
Cognee Docker Setuptopoteretes/cognee32k1 repos~901Automated safety check: NotesApache-2.0

Similar skills

  • Medusa Development

    Mindrally/skills

    Best practices for building commerce applications with Medusa v2, the headless e-commerce framework.

    267 GitHub stars~2.7k tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed
  • Vercel Deploy

    bytedance/deer-flow

    Deploys a project to Vercel with one script and no login, then returns a live preview URL and a claim link for moving the deployment into your own Vercel account.

    83k GitHub starsUsed in 10 repos~797 tokens
    DevOps & CloudAuto-check passed
  • Update V8 Version

    openinterpreter/openinterpreter

    Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.

    69k GitHub starsUsed in 2 repos~845 tokens
    DevOps & CloudAuto-check passed
  • Official

    Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.

    63k GitHub starsUsed in 1 repo~1.3k tokens
    DevOps & CloudAuto-check passed
  • Cognee Docker Setup

    topoteretes/cognee

    Runs the Cognee AI memory platform in Docker, from a one-file prebuilt image to a full compose stack with UI, MCP server, Postgres and Neo4j.

    32k GitHub starsUsed in 1 repo~901 tokens
    DevOps & CloudAuto-check: notes
  • Proxychains Network Fallback

    2025Emma/vibe-coding-cn

    Retries failed network commands through proxychains4 and a local proxy when it sees timeouts, DNS failures or blocked access.

    23k GitHub starsUsed in 1 repo~1.1k tokens
    DevOps & CloudAuto-check: notes

More from medusajs/medusa-agent-skills

All 16 skills in this repo
  • Medusa Internal Admin Agents

    medusajs/medusa-agent-skills

    Walks through adding an AI agent for store operators to a Medusa project: data models, module service, agent runtime, streaming API route and admin chat UI.

    225 GitHub stars~1.9k tokensUpdated 2 days ago
    Auto-check passed
  • Learning Medusa

    medusajs/medusa-agent-skills

    Interactive tutorial where the agent teaches Medusa development by guiding you through building a brands feature, with lessons and verification checkpoints.

    225 GitHub stars~4.1k tokensUpdated 2 days ago
    Auto-check passed
  • Medusa Cloud Deployments CLI

    medusajs/medusa-agent-skills

    Lists Medusa Cloud deployments, fetches one deployment's details and reads backend or storefront build logs through the mcloud CLI to debug failed builds.

    225 GitHub stars~883 tokensUpdated 2 days ago
    Auto-check passed
  • mcloud Environments

    medusajs/medusa-agent-skills

    Runs mcloud environments commands to list, inspect, create, delete, redeploy or rebuild environments in Medusa Cloud projects.

    225 GitHub stars~1.2k tokensUpdated 2 days ago
    Auto-check passed
  • Medusa Cloud Local Build

    medusajs/medusa-agent-skills

    Reproduces a Medusa Cloud build on your machine with mcloud local build, to debug build-failed deployments without pushing or waiting on Cloud.

    225 GitHub stars~1k tokensUpdated 2 days ago
    Auto-check: notes
  • Mcloud Logs

    medusajs/medusa-agent-skills

    Execute mcloud logs to fetch and stream runtime logs for Cloud environments.

    225 GitHub stars~811 tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Medusa Cloud CLI Authentication

What does Medusa Cloud CLI Authentication do?

Runs the mcloud commands for logging in, checking who is authenticated, and choosing the active organization, project and environment. The skill wraps six commands of the Medusa Cloud CLI: `login`, `logout`, `whoami`, `use`, `version` and `signup`. `whoami --json` reports the user, the auth method and the active context, and the skill pipes it through `jq` to confirm the session is authenticated and scoped before any command that changes state.

When should I use Medusa Cloud CLI Authentication?

Medusa Cloud CLI Authentication fits situations like: setting up the Medusa Cloud CLI on a new machine; switching between Medusa Cloud accounts or organizations; checking that a session is authenticated before a deploy or other state-changing command; pointing later commands at a specific project and environment.

How do I install Medusa Cloud CLI Authentication in Claude Code?

Run `npx skills add medusajs/medusa-agent-skills --skill mcloud-auth -a claude-code`. Or copy the skill folder (plugins/medusa-cloud/skills/mcloud-auth in medusajs/medusa-agent-skills) into .claude/skills/mcloud-auth in your project. Claude Code loads it when a task matches its description.

How do I install Medusa Cloud CLI Authentication in Codex?

Run `npx skills add medusajs/medusa-agent-skills --skill mcloud-auth -a codex`. Or copy the skill folder (plugins/medusa-cloud/skills/mcloud-auth in medusajs/medusa-agent-skills) into .agents/skills/mcloud-auth in your project. Codex loads it when a task matches its description.

Can I use Medusa Cloud CLI Authentication in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add medusajs/medusa-agent-skills --skill mcloud-auth -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mcloud-auth, .gemini/skills/mcloud-auth, .github/skills/mcloud-auth and .opencode/skills/mcloud-auth in your project.

What does Medusa Cloud CLI Authentication need to run?

Going by SKILL.md and its folder, Medusa Cloud CLI Authentication needs the command-line tools its instructions call (jq) and credentials named MCLOUD_TOKEN. Our summary lists: The `mcloud` CLI; `jq`; A Medusa Cloud account or an access key in `MCLOUD_TOKEN`. Its frontmatter pre-approves these tools: Bash(mcloud whoami*), Bash(mcloud use*), Bash(mcloud version*), Bash(mcloud logout*), Bash(jq*).

Does Medusa Cloud CLI Authentication access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Medusa Cloud CLI Authentication safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Medusa Cloud CLI Authentication use?

No licence was found for Medusa Cloud CLI Authentication or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Medusa Cloud CLI Authentication use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Medusa Cloud CLI Authentication?

Skills that share tags, products or a category with Medusa Cloud CLI Authentication: Medusa Development (Mindrally/skills, 267 stars), Vercel Deploy (bytedance/deer-flow, 83k stars), Update V8 Version (openinterpreter/openinterpreter, 69k stars) and Analyze GitHub Action Logs (withastro/astro, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Medusa Cloud CLI Authentication?

medusajs (a GitHub organization) maintains it in medusajs/medusa-agent-skills, which has 225 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 5, 2026.

Source: medusajs/medusa-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.