mcloud-logs
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.
- Installs
- 1.3K
- Last 24h
- +14
- Trending rank
- #7164
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/medusajs/medusa-agent-skills --skill mcloud-logs- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads mcloud-logs automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Cloud CLI: Logs Command
Execute mcloud logs to fetch runtime logs for a Cloud environment's backend or storefront.
Constraints
--followand--jsonare incompatible. For programmatic log analysis, use bounded time windows with--from/--toand--json.--followstreams until interrupted withCtrl+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
--fromwithout--toto fetch from a time until now. - Pass
--towithout--fromonly if--tois within the last 15 minutes; otherwise also pass--from. - Both
--fromand--toaccept ISO 8601 timestamps.
FAQ
What does the mcloud-logs skill do?
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.
How do I install mcloud-logs?
Run npx skills add https://github.com/medusajs/medusa-agent-skills --skill mcloud-logs in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/mcloud-logs/ (personal) or .claude/skills/mcloud-logs/ (project).
Which AI agents can use mcloud-logs?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is mcloud-logs safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains mcloud-logs?
It is published by medusajs in medusajs/medusa-agent-skills, and it is an official skill from the maker of the technology it covers. It has 1,328 recorded installs.
More from medusajs/medusa-agent-skills
storefront-best-practices
medusajs/medusa-agent-skills
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, Vue). Provides patterns, decision frameworks, backend integration guidance.
building-with-medusa
medusajs/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.
building-admin-dashboard-customizations
medusajs/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
medusajs/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.
db-migrate
medusajs/medusa-agent-skills
Run database migrations in Medusa
db-generate
medusajs/medusa-agent-skills
Generate database migrations for a Medusa module
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.