Magento 2 Coding Standards MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAGENTO_MCP_THEME_DIR | No | Override the directory for custom theme standards. Defaults to ~/.magento-mcp/themes/ if not provided. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_magento_patternA | 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_codeA | Validate code against Magento 2 coding standards. Returns violations with severity, line numbers, and fix suggestions. |
| check_securityC | Perform security-focused validation on code. Checks for XSS vulnerabilities, SQL injection risks, insecure functions, and other security issues. |
| explain_ruleA | Get detailed explanation of a Magento coding standard rule including reasoning, bad/good examples, and fix suggestions. |
| list_rulesA | 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_summaryB | Get a summary of all Magento coding standard rules grouped by category, showing counts of errors and warnings. |
| manage_themeB | 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 | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose with no overlap: check_security focuses on security validation, explain_rule provides rule details, get_magento_pattern offers coding patterns, get_rules_summary gives rule summaries, list_rules lists rules with filtering, manage_theme handles theme-specific standards, and validate_code performs general code validation. An agent can easily differentiate between them.
The naming is mostly consistent with a verb_noun pattern (e.g., check_security, explain_rule, validate_code), but manage_theme uses a verb_noun format that is slightly different in structure (it implies management rather than a direct action like 'get' or 'list'), and get_magento_pattern includes 'magento' in the name, which deviates from the pure pattern. Overall, it's readable with minor deviations.
With 7 tools, the count is well-scoped for a Magento 2 coding standards server. Each tool serves a specific function in the domain, such as validation, rule explanation, and theme management, without being excessive or too sparse. This aligns with typical MCP server tool counts of 3-15 for focused purposes.
The tool set provides complete coverage for Magento 2 coding standards: it includes validation (validate_code), security checks (check_security), rule exploration (list_rules, explain_rule, get_rules_summary), pattern guidance (get_magento_pattern), and theme management (manage_theme). There are no obvious gaps, covering the full lifecycle from learning to applying standards.