Mcloud Projects

Organization

medusajs

mcloud-projects

Execute mcloud projects commands to list, get, or delete Cloud projects. Use when discovering projects, resolving project handles by name, or retrieving project details including linked environments.

Overview

Publisher	medusajs
Repository	`medusa-agent-skills`
Skill name	`mcloud-projects`
Stars	218
Forks	27
Bundled files	Instructions only
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by medusajs on GitHub. Read the source before you install it.

Installation

Install the Mcloud Projects AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/medusajs/medusa-agent-skills/tree/main/plugins/medusa-cloud/skills/mcloud-projects

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/medusajs/medusa-agent-skills.git /tmp/medusa-agent-skills
mkdir -p .claude/skills
cp -r /tmp/medusa-agent-skills/plugins/medusa-cloud/skills/mcloud-projects .claude/skills/mcloud-projects

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Mcloud Projects in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Mcloud Projects on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Mcloud Projects is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Cloud CLI: Projects Commands

Execute mcloud projects commands to manage Cloud projects.

Constraints

projects delete is irreversible — removes all associated environments, deployments, and resources. Always confirm the project ID/handle before deleting.
Use --yes with delete in non-interactive contexts (scripts, pipelines, agents).

Commands

projects list

List projects in an organization. If --organization is omitted (and no active context org is set), lists projects across all organizations you have access to, grouped by organization.

bash
mcloud projects list --organization <org-id> --json

Options:

-o/--organization <id> — Organization ID (falls back to active context; if unset, lists across all your organizations)
--json — Output as JSON

projects get

Retrieve a single project by its ID or handle.

bash
mcloud projects get <project-id-or-handle> --organization <org-id> --json

Arguments:

project — Project ID or handle (required)

Options:

-o/--organization <id> — Organization ID (falls back to active context; required)
--json — Output as JSON

projects delete

Delete a project by its ID or handle. Irreversible.

bash
mcloud projects delete <project-id-or-handle> \
  --organization <org-id> \
  --yes

Arguments:

project — Project ID or handle (required)

Options:

-o/--organization <id> — Organization ID (falls back to active context; required)
-y/--yes — Skip confirmation prompt (required in non-interactive mode)
--json — Output as JSON

Project Fields (JSON)

Field	Description
`id`	Project ID
`handle`	URL-safe project handle (used in most commands)
`name`	Display name
`status`	`ready` when healthy
`region`	Deployment region (e.g. `us-east-1`)
`repository`	Linked GitHub repository (`owner/repo`)
`root_path`	Root path within the repository
`organization`	Owning organization (`id`, `name`, `created_at`)
`environments`	Array of associated environments (each may include `storefront_environments`)

Examples

bash
# List all projects in an organization
mcloud projects list --organization org_123 --json

# Set context to a project by name
PROJECT_HANDLE=$(
  mcloud projects list --organization org_123 --json \
    | jq -r '.[] | select(.name == "My Store") | .handle'
)
mcloud use --project "$PROJECT_HANDLE"

# Get project details including environments
mcloud projects get my-store --organization org_123 --json

# List all environment handles for a project
mcloud projects get my-store --organization org_123 --json \
  | jq -r '.environments[].handle'

# Find project handle by name
mcloud projects list --organization org_123 --json \
  | jq -r '.[] | select(.name == "My Store") | .handle'

# Delete a project (irreversible — confirm before running)
mcloud projects delete old-project --organization org_123 --yes

Frequently asked questions

What does the Mcloud Projects AI skill do?

Execute mcloud projects commands to list, get, or delete Cloud projects. Use when discovering projects, resolving project handles by name, or retrieving project details including linked environments.

Why use Mcloud Projects on TypingMind?

Because you install it once and use it with any model. Mcloud Projects is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Mcloud Projects in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/medusajs/medusa-agent-skills/tree/main/plugins/medusa-cloud/skills/mcloud-projects. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Mcloud Projects?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Mcloud Projects?

As many as you like. As long as a model supports skills, you can use Mcloud Projects with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Mcloud Projects AI skill free?

It is published on GitHub by medusajs. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Setup Deploy

garrytan

CommunityPopular

Configure deployment settings for /land-and-deploy.

Caveman Compress

Compress a memory file such as CLAUDE.md or a todo list into caveman format to save input tokens, keeping a readable backup. Trigger: /caveman-compress.

Caveman Discover

Find and label every LLM workflow in the repository so Caveman Cloud groups spend by workflow instead of one bucket. Use for "discover workflows" or breaking LLM spend down by workflow.

Caveman Manage

Inspect Caveman Cloud's experiment lifecycle and block unsafe execution. Use when asked to start, approve, cancel, promote or roll back a Caveman experiment.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Cloud CLI: Projects Commands

Constraints

Commands

projects list

projects get

projects delete

Project Fields (JSON)

Examples

Frequently asked questions

Related AI Skills

Set up your own AI workspace now