medusajs/medusa-agent-skills

mcloud-logs

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

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/medusajs/medusa-agent-skills --skill mcloud-logs

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

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

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

Options

OptionDescriptionDefault
-o/--organization <id>Organization IDActive context
-p/--project <id-or-handle>Project ID or handleActive context
-e/--environment <handle>Environment handleActive context
-f/--followStream 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 --fromnow
--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 querybackend
--jsonOutput as JSON (incompatible with --follow)false

Examples

bash
# 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.

Related by task

from this repository

More skills

All skills
medusajs
Official

building-admin-dashboard-customizations

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.

1h installs
2
GitHub stars
237
Updated
Nov 13
medusajs
Official

storefront-best-practices

ALWAYS use this skill when working on ecommerce storefronts, online stores, shopping sites. Use for ANY storefront component including checkout pages, cart, payment flows, product pages, product listings, navigation, homepage, or ANY page/component in a storefront. CRITICAL for adding checkout, implementing cart, integrating Medusa backend, making a store agent-friendly for AI shopping agents, or building any ecommerce functionality. Framework-agnostic (Next.js, SvelteKit, TanStack Start, React,

1h installs
2
GitHub stars
234
Updated
Oct 21
medusajs
Official

building-storefronts

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.

1h installs
1
GitHub stars
234
Updated
Oct 21
medusajs
Official

creating-internal-agents

Use when building an internal admin-facing AI agent in a Medusa project. These agents are operated by merchants and store operators — not customers. Covers data models, module service, agent runtime (tools, system prompt, streamText), streaming API routes (NDJSON), and admin UI chat extensions. Load for any internal agent type: store operations assistant, product audit, cohort analysis, customer service tooling for support staff, etc. Do NOT use for customer-facing agents (storefront chatbots, b

1h installs
1
GitHub stars
234
Updated
Oct 21