Magento 2 Development MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-di-preferencesB | Get Magento 2 dependency injection preferences list using magerun2 |
| cache-cleanC | Clear specific Magento 2 cache types or all caches |
| cache-flushC | Flush specific Magento 2 cache types or all caches |
| cache-enableC | Enable specific Magento 2 cache types |
| cache-disableC | Disable specific Magento 2 cache types |
| cache-statusB | Check the status of Magento 2 cache types |
| cache-viewC | Inspect specific cache entries in Magento 2 |
| dev-module-listC | List all Magento 2 modules and their status |
| dev-module-observer-listC | List all Magento 2 module observers |
| dev-module-createC | Create and register a new Magento 2 module |
| sys-infoC | Get Magento 2 system information |
| sys-checkB | Check Magento 2 system requirements and configuration |
| config-showC | View Magento 2 system configuration values |
| config-setC | Set Magento 2 system configuration values |
| config-store-getC | Get store-specific Magento 2 configuration values |
| config-store-setC | Set store-specific Magento 2 configuration values |
| db-queryC | Execute SQL queries directly on Magento 2 database |
| setup-upgradeC | Run Magento 2 setup upgrade to update database schema and data |
| setup-di-compileB | Compile Magento 2 dependency injection configuration |
| setup-db-statusA | Check Magento 2 database status to see if setup:upgrade is needed |
| setup-static-content-deployC | Deploy Magento 2 static content and assets |
| sys-store-listB | List all Magento 2 stores, websites, and store views |
| dev-theme-listB | List all available Magento 2 themes |
| sys-store-config-base-url-listC | List all base URLs for Magento 2 stores |
| sys-cron-listB | List all Magento 2 cron jobs and their configuration |
| sys-url-listB | Get all Magento 2 URLs |
| sys-website-listC | List all Magento 2 websites |
| sys-cron-runC | Run Magento 2 cron jobs |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 28 tools
Most tools have distinct purposes with clear boundaries, such as cache-clean vs. cache-flush or config-set vs. config-show. However, some tools like sys-store-list and sys-website-list could potentially overlap in listing store-related information, though their descriptions specify different scopes (stores/websites vs. websites only). Overall, the naming and descriptions help minimize confusion.
Tool names follow a highly consistent verb-noun pattern with hyphens, such as cache-clean, config-set, and sys-info. All tools adhere to this convention, making them predictable and easy to parse. There are no deviations in style or mixed conventions.
With 28 tools, the count is on the higher side for a development server, bordering on heavy. While it covers many aspects of Magento 2 development, it may feel overwhelming or redundant in some areas, such as multiple cache-related tools. A more streamlined set could improve usability without losing functionality.
The tool set provides comprehensive coverage for Magento 2 development, including cache management, configuration, database operations, module and theme development, system setup, and system information. It supports full lifecycle operations like creating modules, deploying content, and running upgrades, with no obvious gaps that would hinder agent workflows.