Index of every page on this site: llms.txt
All skills
medusajs avatar

/mcloud-logs

@c5a56b4 official
by Medusamedusajs/medusa-agent-skills237 stars
29
Run it yourself

Execute mcloud logs to fetch and stream runtime logs for Cloud environments. Use when reading backend or storefront logs, filtering by time range, searching for errors, or scoping logs to a specific deployment.

Use this Skill: https://skilld.dev/gh/medusajs/medusa-agent-skills/mcloud-logs

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈56 tokens for metadata: the name and description. ≈740 when used: this file.

Description uses 2.8% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈224 characters, or 2.8%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Cloud CLI: Logs Command

Execute mcloud logs to fetch runtime logs for a Cloud environment's backend or storefront.

Constraints

  • --follow and --json are incompatible. For programmatic log analysis, use bounded time windows with --from/--to and --json.
  • --follow streams until interrupted with Ctrl+C — do not use in scripts or pipelines.
  • Default retrieves the last 500 log lines from the past 15 minutes.

Command

mcloud logs \
  --organization <org-id> \
  --project <project-id-or-handle> \
  --environment <environment-handle> \
  [options]

Options

Option Description Default
-o/--organization <id> Organization ID Active context
-p/--project <id-or-handle> Project ID or handle Active context
-e/--environment <handle> Environment handle Active context
-f/--follow Stream logs continuously (incompatible with --json) false
--limit <1-5000> Max log lines (non-follow mode only) 500
--from <ISO8601> Start of time range (e.g. 2026-04-22T10:00:00Z) 15 minutes ago
--to <ISO8601> End of time range; if >15 min ago, must also pass --from now
--search <string> Filter by substring (same as dashboard search bar) —
--deployment <id> Filter by deployment or build ID —
--source <string> Filter by source (repeatable) —
--metadata <key=value> Filter by metadata field (repeatable; same key merges values) —
--type <backend|storefront> Log stream to query backend
--json Output as JSON (incompatible with --follow) false

Examples

# Basic log fetch (last 500 lines, last 15 min)
mcloud logs --json

# Search for errors
mcloud logs --search error --limit 1000 --json

# Filter for HTTP 500 errors via metadata
mcloud logs --metadata status=500 --limit 1000 --json

# Logs for a specific deployment (build or deployment ID)
mcloud logs --deployment bld_01ABC123 --json

# Structured output for agent analysis
mcloud logs --search error --json | jq '.[] | {timestamp, source, message}'

# Storefront logs
mcloud logs --type storefront --json

# Stream live logs (human-readable, not for scripts)
mcloud logs --follow

# Logs within a specific time range
mcloud logs --from 2026-04-22T10:00:00Z --to 2026-04-22T11:00:00Z --limit 1000 --json

# Logs from a time until now
mcloud logs --from 2026-04-22T10:00:00Z --json

# Multiple source filters
mcloud logs --source api --source worker --json

# Multiple metadata filters (HTTP 4xx and 5xx)
mcloud logs --metadata status=400 --metadata status=500 --limit 500 --json

Time Range Notes

  • Default window is the past 15 minutes.
  • Pass --from without --to to fetch from a time until now.
  • Pass --to without --from only if --to is within the last 15 minutes; otherwise also pass --from.
  • Both --from and --to accept ISO 8601 timestamps.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill allows the agent to interact with Medusa Cloud logs using the official mcloud CLI tool. It is a standard administrative utility for monitoring and debugging environments with no signs of malicious intent or suspicious behavior.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: MEDIUM · 1 issue

Signed by skilld at c5a56b4. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 7 months ago
What it can do
Runs commands
All 2 allowed tools
Bash(mcloud logs*)Bash(jq*)

README badge

README badge for medusajs/medusa-agent-skills/mcloud-logs