Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAGENTO_MCP_THEME_DIR | No | Optional environment variable to override the default directory for custom theme standards (~/.magento-mcp/themes/). |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_magento_pattern | Get the correct Magento 2 way to accomplish a task. Returns the proper pattern, code example, and what to avoid. Use this for "vibe coding" - writing Magento-compliant code naturally. |
| validate_code | Validate code against Magento 2 coding standards. Returns violations with severity, line numbers, and fix suggestions. |
| check_security | Perform security-focused validation on code. Checks for XSS vulnerabilities, SQL injection risks, insecure functions, and other security issues. |
| explain_rule | Get detailed explanation of a Magento coding standard rule including reasoning, bad/good examples, and fix suggestions. |
| list_rules | List all Magento coding standard rules. Can filter by category (Security, Legacy, PHP, Functions, Templates, Less, etc.), minimum severity (1-10), or search term. |
| get_rules_summary | Get a summary of all Magento coding standard rules grouped by category, showing counts of errors and warnings. |
| manage_theme | Manage theme-specific coding standards. Themes layer additional rules on top of base Magento standards. Built-in presets: hyva (Alpine.js + TailwindCSS), luma (jQuery + RequireJS + LESS), breeze (Vanilla JS), porto (Luma-based + Porto widgets). Custom themes can be added as JSON files. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |