Overview
Medusa provides development plugins for its backend, admin UI and storefront. Merchants with a development team can use them to extend a custom commerce stack.
Who it suits
Commerce engineering teams building or extending a Medusa backend, admin interface, or custom storefront and wanting the assistant to follow Medusa’s architectural conventions.
Who it may not suit
Shopify merchants seeking an installable operations app, or teams without developers to own a custom commerce system.
Seller use cases
- A Medusa backend needs a new business module → consult medusa-dev patterns → prepare an implementation that fits the existing module and workflow structure.
- A team is building product and cart screens → load ecommerce-storefront → turn storefront requirements into a reviewed development checklist.
- A new developer needs to understand Medusa concepts → follow the learn-medusa brands example → use the example as learning material before changing the real store.
What you can do
What you need
- Claude Code and an existing or planned Medusa project; development skills require coding knowledge.
Install
Claude Code
/plugin marketplace add medusajs/medusa-agent-skills
/plugin install medusa-dev@medusa Installation source ↗Permissions & data
The development plugin reads local code and public documentation. Installing Cloud skills adds account and deployment operations through mcloud.
Project info
- Maintainer
- medusajs
- GitHub stars at check date
- 234
- Last commit
- 2026-10-21
- License
- Not specified
- Last checked
- 2026-10-30
Pricing at a glance
The repository lists plugin installation without a separate skill price. Running the resulting commerce application may require hosting and model usage. No repository-level license was identified in the reviewed project snapshot.
FreeGood to know
The development and storefront plugins provide coding guidance, not a hosted store. The separate medusa-cloud plugin can operate authenticated cloud resources; installing it changes the permissions you need to consider.
Alternatives to Medusa Agent Skills
Shopify Agent Skills New
Find Shopify API documentation for an implementation question
ShopifyShopify’s skills target hosted Shopify APIs and themes; Medusa’s target a commerce application your team builds and runs.
Agentic Commerce Skills & Plugins New
Inspect public storefront discovery and structured-data surfaces
Any storeAgentic Commerce Skills concentrate on discovery and checkout protocols, which is a narrower integration concern than building the Medusa storefront itself.
Saleor MCP New
Retrieve product information from a Saleor instance
SaleorSaleor MCP reads an existing Saleor store’s operational data, while Medusa skills guide development of a different commerce stack.
Frequently asked questions
Do I need all four Medusa plugins?
Choose the plugin for your task. Backend and admin development, learning, storefront work, and cloud resource management are separate entries with different purposes.
Does copying skills also install the documentation MCP?
No. The README distinguishes copying instruction files with the skills command from configuring the MCP server; another agent may need both assets copied separately.
Can I use these instructions outside Claude Code?
Yes. The project describes manual installation for other agents, including placing skills and the documentation connection in the agent’s project configuration.
What account does the development plugin inspect?
Its documentation connection queries public Medusa documentation. Authenticated cloud administration belongs to the separate Cloud plugin and requires the corresponding CLI access.
Checked against the official site on 2026-10-30 · Official source ↗
Sources
- Project repository · 2026-10-30
- README at reviewed commit · 2026-10-30
- Project documentation / source: plugins/ecommerce-storefront/skills/storefront-best-practices/SKILL.md · 2026-10-30