On GitHub, magento/magento2-phpstorm-plugin has picked up 465 stars, Backend, Java. PHPStorm Plugin for Magento 2
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
PhpStorm IDE Plugin for a better Magento 2 development workflow.
Support the Project
If you find this plugin helpful and want to support its development, consider buying the contributors a coffee:
( (
) )
........
| |]
\ /
`----'
Buy Me a Coffee
Sponsors
Thank you to our sponsors for supporting the plugin:
Lucas van Staden
Ivan Chepurnyi
Michael Ryvlin
Features
Configuration smart completion and references for XML/JavaScript files
Navigate to configuration reference in scope of class/interface
Go to plugin reference in scope of class/interface and method
Navigate to Web API configuration reference in scope of class/interface and method
Plugin class methods generation
Plugin declaration inspection
Magento-specific MCP tools for AI agents
RequireJS reference navigation and completion
MFTF reference navigation and completion
GraphQL navigation line markers
Code generation
Inspections for XML configuration
Installation
Go to Settings > Preferences in the PhpStorm IDE
Navigate to Plugins
Click the Browse repositories... button and search for "Magento 2 and Adobe Commerce"
Install the plugin and restart PhpStorm
Go to Settings > Preferences > Languages & Frameworks > PHP > Frameworks > Magento in the PhpStorm IDE
Check Enable and click the OK button
Works with
PhpStorm 2026+
MCP tools
Connect your AI assistant to PhpStorm to inspect Magento configuration, generate modules and other components, and check upgrade compatibility.
Open your Magento project and enable the plugin in Settings > Languages & Frameworks > PHP > Frameworks > Magento. Check the Magento installation path if it differs from the project directory.
Enable the IDE's MCP Server and add its connection to your assistant using the configuration shown in the IDE.
Wait for indexing to finish, then ask your assistant to work with the open project. For example:
“Find the plugins and observers used by Application_Blog.”
“Create a Magento module named Acme_Example.”
“Check Application_Blog against the next published Magento minor release and explain the findings.”
Compatibility checks can download release data on first use. Ask for only new upgrade issues to exclude issues already present in the installed version. The checks cover Magento Open Source core APIs; review Commerce extensions, third-party code, and runtime behavior separately.
In the Magento settings page, you can also:
Install the bundled Magento inspect and Magento scaffold skills for your assistant.
Set MCP CLI wrapper candidates when your project uses Docker or other wrapper scripts, for example bin/magento, bin/cli, bin/composer.
Change Published releases URL to use a GitHub-compatible release catalog mirror. Leave it blank to use the official Magento GitHub catalog.
Reconnect your assistant after updating the plugin so it discovers the latest tools. If it connects to the wrong project, check the IDE connection and project path. When running multiple IDEs, ensure their MCP servers use different ports.
Setting up development environment
Check out this repository.
Open the project in IntelliJ IDEA.
Make sure that you are on the latest develop branch (for example 5.4.0-develop).
Import the Gradle project from build.gradle.kts.
Use JDK 25 for both the project SDK and the Gradle JVM:
Right click on the project root > Open Module Settings > Project > Project SDK
In the Gradle tool window, run Tasks > Intellij platform > runIde.
The task launches a PhpStorm sandbox with the plugin installed. Make sure the plugin is enabled and indexing is finished before testing features.
To run ./gradlew test, also install PHP CLI and add php (php.exe on Windows) to PATH. The run-configuration tests launch PHP to verify interpreter settings and command arguments. CI installs PHP 8.4 on Linux, Windows, and macOS.
How to contribute
Start with looking into Community Backlog. Any ticket in Ready for Development and Good First Issue columns are a good candidates to start.
Didn't satisfy your requirements? Create a new issue. It can be for example:
Bug report - Found a bug in the code? Let us know!
Enhancement - Know how to improve existing functionality? Open an issue describe how to enhance the plugin.
New feature proposal - Know how to make a killer feature? Do not hesitate to submit your proposal.
The issue will appear in the Ready for Grooming column of the Community Backlog. Once it will be discussed and approved the issue will be ready for development.
Refer to the Contributing Guide for more information on how to contribute.
Learn to contribute
SDK Developing a Plugin
Good Presentation about platform How We Built Comma, the Raku IDE, on the IntelliJ Platform
Plugin example idea-php-symfony2-plugin
How to create SandBox for development
Create sandbox folder
Copy to sandbox folder composer.json and composer.lock
In sandbox folder create app/code and vendor/magento
Copy any of the magento modules (as for example: framework, module-catalog, module-checkout, module-customer, module-sales) into the vendor/magento folder. It is better to add as few modules as possible to reduce reindexing time during application running
(Nice to have) Open IDE and go to Preferences > Editor > File and Code Templates > Includes tab and add default headers for PHP File Header and XML File Header
How active is development on magento/magento2-phpstorm-plugin?
The most recent commit recorded on magento/magento2-phpstorm-plugin was 13 days ago, based on the GitHub push timestamp. The repository has 98 forks — one of the better signals of community interest.
How many stars does magento/magento2-phpstorm-plugin have?
magento/magento2-phpstorm-plugin has 465 GitHub stars — refresh the page for the live number, or check github.com/magento/magento2-phpstorm-plugin. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
What else is in the Backend space?
magento/magento2-phpstorm-plugin is tracked by TopGit under the Backend category, alongside 12 GitHub-tagged topics. Trending and Topics pages list peer repositories of comparable stars and language.
What language is magento/magento2-phpstorm-plugin written in?
magento/magento2-phpstorm-plugin is written primarily in Java. GitHub's language field is based on the largest share of bytes in the default branch.
What topics is magento/magento2-phpstorm-plugin associated with?
Where do I read more about magento/magento2-phpstorm-plugin?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/magento/magento2-phpstorm-plugin is the definitive source.
Why is magento/magento2-phpstorm-plugin categorized under Backend?
TopGit places magento/magento2-phpstorm-plugin in the Backend category based on its GitHub topics and description (tagged: "hacktoberfest", "intellij", "intellij-plugin"). Categories are assigned from real repository metadata, not editorial guesswork.
Read full README in the tab above.
Want a second opinion on magento2-phpstorm-plugin?
Ask an AI that can read this page — one click and you get its take on magento2-phpstorm-plugin.