
Mcloud Logs
This pulls runtime logs from your Cloud environments using the mcloud CLI. You can fetch backend or storefront logs, filter by time range, search for specific strings, or scope to a deployment ID. The JSON output mode works well for piping through jq when you're hunting down errors or analyzing patterns, though you'll need to use bounded time windows since JSON and live streaming don't mix. Default behavior grabs the last 500 lines from the past 15 minutes, which is usually enough for a quick check. The metadata filters are handy for zeroing in on HTTP status codes or other structured fields without regex wrangling.
- skills.sh installs
- 1.5K
- GitHub stars
- 236
- last updated
- Aug 21, 2026
Install
$ npx -y skills add medusajs/medusa-agent-skills --skill mcloud-logs --agent claude-codeInstalls into .claude/skills of the current project.
Files
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
Sponsors
Details
- Repository
- github.com/medusajs/medusa-agent-skills
- Categories
- Backend & APIs, AI & Agent Building, Cloud & Infrastructure
- First seen
- Jun 3, 2026
More from medusajs/medusa-agent-skills
All 15- Mcloud Organizations1.5K
- Storefront Best Practices5K
- Building With Medusa4.8K
- Building Admin Dashboard Customizations4.7K
- Building Storefronts4.4K
- Db Migrate3.7K
- Db Generate3.6K
- Learning Medusa3.6K
- New User3.2K
- Using Medusa Cloud1.6K
- Mcloud Deployments1.5K
- Mcloud Variables1.5K
- Mcloud Environments1.5K
- Mcloud Projects1.5K