What can you do with this server?

The Magento 2 Development MCP Server provides comprehensive Magento 2 development and administration tools through AI agents (Claude, Cursor, etc.), covering the following areas: DI & Module Management * Retrieve DI preferences across scopes (global, adminhtml, frontend, etc.) * List modules (with enabled/disabled filtering), observers (filterable by event), and themes * Create new modules with optional components (blocks, helpers, models, composer.json, readme, strict types) * Inspect plugin/interceptor chains for any class or method across all DI scopes Cache Management * Clean, flush, enable, disable, and check status of specific or all cache types * Inspect individual cache entries by key System Diagnostics * Retrieve system information and verify system requirements/configuration health Configuration Management * View and set system configuration values by path, scope, and scope ID (with optional encryption) * Get and set store-level configuration values Database Tools * Execute raw SQL queries against the Magento 2 database * Check database status to determine if setup:upgrade is needed Setup & Deployment * Run setup upgrades (with option to keep generated files) * Compile DI configuration * Deploy static content with options for languages, themes, parallel jobs, and force deployment Store & Website Management * List stores, websites, store views, base URLs, and all URLs (filterable by store ID) Cron Management * List all cron jobs and their configuration * Run specific cron jobs or entire cron groups Additional Features * Automatic detection of Docker environments (Warden, DDEV, docker-magento, docker-compose) * Flexible output formats: table, JSON, and CSV * Support for custom magerun2 binary paths via environment variables, with automatic fallback to local execution

Which integrations are available for this server?

Enables creation of Magento 2 modules with composer.json files for dependency management and package distribution Provides access to Magento 2's GraphQL API context through dependency injection preference management Generates PHP code for Magento 2 modules including blocks, helpers, models, and setup scripts with strict type declarations

How do I use Magento 2 Development MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Magento 2 Development MCP Server list all modules and show which ones are enabled" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

Magento 2 Development MCP Server

A Model Context Protocol (MCP) server for Magento 2 development, designed to integrate with AI agents like Claude, Cursor, Continue.dev, and Augment Code.

Installation

Using npx

npx -y @elgentos/magento2-dev-mcp

Quick Start

Add to your AI agent's MCP configuration:

{ "mcpServers": { "magento2-dev": { "command": "npx", "args": ["-y", "@elgentos/magento2-dev-mcp"] } } }

Restart your AI agent to load the MCP server
Start using Magento 2 development tools through your AI agent!

See AI Platform Configuration Examples for platform-specific setup instructions.

Docker Environment Support

The server automatically detects Docker-based Magento environments and routes magerun2 commands through the container:

Environment	Detection	Command prefix
Warden	`WARDEN_ENV_TYPE` in `.env`	`warden shell -c '...'`
DDEV	`.ddev/` directory	`ddev exec ...`
docker-magento	`bin/clinotty` file	`bin/clinotty ...`
docker-compose	`docker-compose.yml` or `compose.yaml`	`docker compose exec -T <service> ...`

For docker-compose the server tries the service names phpfpm, php-fpm, and php in order.

If Docker execution fails, the server falls back to running magerun2 locally.

Environment Variables

Variable	Description	Default
`MAGERUN2_COMMAND`	Override the magerun2 binary name or path	`magerun2`

Use MAGERUN2_COMMAND when your system installs the binary under a different name (e.g. n98-magerun2) or when you need to specify an absolute path:

{ "mcpServers": { "magento2-dev": { "command": "npx", "args": ["-y", "@elgentos/magento2-dev-mcp"], "env": { "MAGERUN2_COMMAND": "n98-magerun2" } } } }

Features

DI & Module Tools

Parameters:

scope (optional): The scope to get DI preferences for
- Options: global, adminhtml, frontend, crontab, webapi_rest, webapi_soap, graphql, doc, admin
- Default: global

Available Scopes:

global - Global scope (default)
adminhtml - Admin area
frontend - Frontend/storefront area
crontab - Cron job execution context
webapi_rest - REST API context
webapi_soap - SOAP API context
graphql - GraphQL API context
doc - Documentation context
admin - Admin context (alternative to adminhtml)

Parameters:

format (optional): Output format (table, json, csv) - Default: table
enabled (optional): Show only enabled modules
disabled (optional): Show only disabled modules

Parameters:

format (optional): Output format (table, json, csv) - Default: table
event (optional): Filter by specific event name

Parameters:

format (optional): Output format (table, json, csv) - Default: table

Parameters:

vendorNamespace (required): Namespace (your company prefix)
moduleName (required): Name of your module
minimal (optional): Create only module file
addBlocks (optional): Add blocks
addHelpers (optional): Add helpers
addModels (optional): Add models
addSetup (optional): Add SQL setup
addAll (optional): Add blocks, helpers and models
enable (optional): Enable module after creation
modman (optional): Create all files in folder with a modman file
addReadme (optional): Add a readme.md file to generated module
addComposer (optional): Add a composer.json file to generated module
addStrictTypes (optional): Add strict_types declaration to generated PHP files
authorName (optional): Author for readme.md or composer.json
authorEmail (optional): Author email for readme.md or composer.json
description (optional): Description for readme.md or composer.json

Example Usage:

{ "name": "dev-module-create", "arguments": { "vendorNamespace": "MyCompany", "moduleName": "CustomModule", "addAll": true, "enable": true, "addReadme": true, "addComposer": true, "authorName": "John Doe", "authorEmail": "john@example.com", "description": "A custom Magento 2 module" } }

Analyzes di.xml files across all DI scopes to find plugins for a given class. Resolves the full class hierarchy (parent classes and interfaces) so inherited plugins are included. Returns the plugin list, sort order, and full execution order chain per scope.

Parameters:

className (required): Fully qualified PHP class or interface name
methodName (optional): Method name to inspect. Omit to scan all public methods.

Example — single method:

{ "name": "dev-plugin-list", "arguments": { "className": "Magento\\Catalog\\Api\\ProductRepositoryInterface", "methodName": "save" } }

Example — scan all methods of a class:

{ "name": "dev-plugin-list", "arguments": { "className": "Magento\\Framework\\View\\LayoutInterface" } }

Scopes checked: global, adminhtml, frontend, crontab, webapi_rest, webapi_soap, graphql

Docker support: Automatically detects Warden, DDEV, docker-magento, and docker-compose environments. Falls back to local PHP.

System Diagnostics

Parameters:

format (optional): Output format (table, json, csv) - Default: table

Parameters: None

Cache Management

Available Tools:

cache-clean - Clear specific or all caches
cache-flush - Flush specific or all caches
cache-enable - Enable specific cache types
cache-disable - Disable specific cache types
cache-status - Check cache status
cache-view - Inspect cache entries

See Cache Types Reference for details.

Configuration Management

Parameters:

path (optional): Configuration path to show
scope (optional): Configuration scope (default, website, store)
scopeId (optional): Scope ID (website ID or store ID)

Parameters:

path (required): Configuration path to set
value (required): Value to set
scope (optional): Configuration scope
scopeId (optional): Scope ID
encrypt (optional): Encrypt the value

Store-specific configuration management for getting and setting configuration values at the store level.

Database Tools

Parameters:

query (required): SQL query to execute
format (optional): Output format (table, json, csv) - Default: table

Setup & Deployment

Parameters:

keepGenerated (optional): Keep generated files during upgrade

Parameters: None

Parameters:

languages (optional): Languages to deploy
themes (optional): Themes to deploy
jobs (optional): Number of parallel jobs
force (optional): Force deployment

Store Management

Parameters:

format (optional): Output format (table, json, csv) - Default: table

Parameters:

format (optional): Output format (table, json, csv) - Default: table

Parameters:

format (optional): Output format (table, json, csv) - Default: table
storeId (optional): Store ID to filter URLs

Parameters:

format (optional): Output format (table, json, csv) - Default: table

Cron Management

Parameters:

format (optional): Output format (table, json, csv) - Default: table

Parameters:

job (optional): Specific cron job to run
group (optional): Cron group to run

License

MIT License - see LICENSE file for details.

Install Server

A

security – no known vulnerabilities

A

license - permissive license

A

quality - confirmed to work

How are these scores calculated?

Resources

Need Help?

Report Issue

Related Servers

Tools

View all tools

Magento 2 Development MCP Server

Magento 2 Development MCP Server

Installation

Using npx

Quick Start

Docker Environment Support

Environment Variables

Features

DI & Module Tools

System Diagnostics

Cache Management

Configuration Management

Database Tools

Setup & Deployment

Store Management

Cron Management

License

Resources

Tools

Latest Blog Posts

MCP directory API