Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
medusajs avatar

Mcloud Variables

  • 669 installs
  • 207 repo stars
  • Updated July 31, 2026
  • medusajs/medusa-agent-skills

mcloud-variables is a Claude Code skill that executes mcloud variables CLI commands to list and inspect Medusa Cloud environment variables and secrets for developers configuring DB URLs, payment keys, and third-party tok

About

mcloud-variables is a Claude Code skill from medusajs/medusa-agent-skills that runs mcloud variables commands to inspect environment variables across Medusa Cloud projects and environments. The skill lists and retrieves configuration keys for database URLs, payment provider keys, and third-party API tokens while enforcing a safety rule to never pass --reveal unless the user explicitly requests secret values. Developers reach for mcloud-variables when preparing or auditing Medusa Cloud deploys and need to confirm which variables exist per environment without manually opening the dashboard. Lookups require --project and --environment flags, and output can be piped through jq for structured inspection.

  • Per-environment secret management
  • Payment and DB credential setup
  • Safe variable rotation
  • Pre-deploy configuration checks
  • mcloud env var APIs

Mcloud Variables by the numbers

  • 669 all-time installs (skills.sh)
  • +74 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #227 of 1,435 DevOps & CI/CD 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-variables

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs669
repo stars207
Last updatedJuly 31, 2026
Repositorymedusajs/medusa-agent-skills

How do you list Medusa Cloud environment variables?

Set and rotate Medusa Cloud environment variables and secrets before deploy when configuring DB URLs, payment keys, and third-party tokens safely per environment.

Who is it for?

Medusa Cloud developers auditing or configuring environment variables and secrets across project environments before a deploy without exposing values via --reveal unless explicitly requested.

Skip if: Self-hosted Medusa deployments using local .env files where the mcloud CLI and Medusa Cloud project/environment flags do not apply.

When should I use this skill?

A Medusa Cloud deploy needs environment variables inspected, listed, or verified and mcloud variables commands with project and environment flags are required.

What you get

mcloud variables command output listing environment keys, per-environment variable values or metadata, and jq-filtered inspection results.

  • Environment variable listings
  • Per-key variable inspection output

Files

SKILL.mdMarkdownGitHub ↗

Cloud CLI: Variables Commands

Execute mcloud variables commands to inspect environment variables for Cloud environments.

Constraints

  • Never pass `--reveal` unless the user explicitly asks. Secret values appear in terminal scrollback, log aggregators, and process listings.
  • Looking up by key requires --project and --environment (or the equivalent in active context). Looking up by ID (var_...) works without project/environment context.

Commands

variables list

List all environment variables for a Cloud environment.

mcloud variables list \
  --organization <org-id> \
  --project <project-id-or-handle> \
  --environment <environment-handle> \
  --json

Options:

  • -o/--organization <id> — Organization ID (falls back to active context)
  • -p/--project <id-or-handle> — Project ID or handle (falls back to active context)
  • -e/--environment <handle> — Environment handle (falls back to active context)
  • --reveal — Print secret values in plaintext instead of masking (use only when explicitly asked)
  • --limit <1-500> — Max results (default: 200)
  • --offset <number> — Pagination offset (default: 0)
  • --json — Output as JSON

variables get

Retrieve a single variable by its ID (var_...) or key.

# By key (requires project + environment context)
mcloud variables get ADMIN_CORS \
  --organization <org-id> \
  --project <project-id-or-handle> \
  --environment <environment-handle> \
  --json

# By ID (works without project/environment context)
mcloud variables get var_01XYZ --json

Arguments:

  • variable — Variable ID (var_...) or key (required)

Options:

  • -o/--organization <id>, -p/--project <id-or-handle>, -e/--environment <handle>
  • --reveal — Print secret value in plaintext (use only when explicitly asked)
  • --json — Output as JSON

Variable Fields (JSON)

FieldDescription
idVariable ID (var_...)
keyVariable name (e.g. ADMIN_CORS)
valueVariable value (masked if is_secret and --reveal not passed)
is_secretWhether the variable is treated as a secret
is_buildAvailable at build time
is_runtimeAvailable at runtime
entity_idThe environment ID this variable belongs to

Examples

# List all variables for the active environment
mcloud variables list --json

# Get a variable by key (with active context)
mcloud variables get DATABASE_URL --json

# Get a variable by ID (no env context needed)
mcloud variables get var_01XYZ --json

# Only reveal secrets when user explicitly asks
mcloud variables get STRIPE_SECRET_KEY --reveal --json | jq -r '.value'

# Export all variables to a .env file (user must explicitly request --reveal)
mcloud variables list --reveal --json \
  | jq -r '.[] | "\(.key)=\(.value)"' \
  > .env

# List only runtime variables
mcloud variables list --json | jq '[.[] | select(.is_runtime == true)]'

# Check if a specific variable exists
mcloud variables list --json | jq '.[] | select(.key == "REDIS_URL")'

Related skills

FAQ

When does mcloud-variables use the --reveal flag?

mcloud-variables never passes --reveal unless the user explicitly requests secret values. Secret output appears in terminal scrollback and logs, so the skill defaults to metadata-only inspection of Medusa Cloud variables.

What flags are required for mcloud variable lookups?

mcloud-variables requires --project and --environment flags when looking up variables by key in Medusa Cloud. The skill executes mcloud variables list and get commands scoped to the target cloud environment.

DevOps & CI/CDinfradeploy

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.