Symfony Plugin - Latest Features
Newest features for Symfony development in PhpStorm
2026-01-17
Generates Symfony service definitions in YAML or XML format for a given PHP class. This MCP tool analyzes a class constructor to identify dependencies and creates service arguments for explicit wiring.
The tool supports both YAML (default) and XML output formats, with options to use the class name as service ID or generate a short ID.
YAML example:
App\Service\EmailService:
arguments: ['@mailer', '@logger']XML example:
<service id="App\Service\EmailService">
<argument type="service" id="mailer"/>
</service>2026-01-17
Completion UX Html Twig
Auto-completes Stimulus controller names in HTML data-controller attributes and Twig stimulus_controller() function calls. The completion shows all registered Stimulus controllers from the project, including those from Symfony UX packages.
In HTML, normalized names are provided (e.g., symfony--ux-chartjs--chart). In Twig, both normalized names and original module names (e.g., @symfony/ux-chartjs/chart) are supported. Navigation from controller name to the source JavaScript file is also available.
HTML - data-controller attribute:
<div data-controller="symfony--ux-chartjs--chart">
<canvas data-symfony--ux-chartjs--chart-target="canvas"></canvas>
</div>Twig - stimulus_controller() function:
{{ stimulus_controller('symfony--ux-chartjs--chart', {
'data': chartData
}) }}2026-01-14
Lists all available options for a specific Symfony form type. This MCP tool provides detailed information about option names, their types (DEFAULT, REQUIRED, DEFINED), and the source classes that define them.
The tool accepts a form type name or FQN and returns CSV format with columns: name, type, source.
name,type,source
label,DEFAULT,Symfony\Component\Form\Extension\Core\Type\FormType
required,DEFAULT,Symfony\Component\Form\Extension\Core\Type\FormType
data,DEFAULT,Symfony\Component\Form\Extension\Core\Type\FormType2026-01-14
Lists the last 10 Symfony profiler requests with detailed information about HTTP requests, controllers, routes, templates, and form types used. This MCP tool provides optional filtering by URL, hash, controller, and route name.
The tool returns CSV format with columns: hash, method, url, statusCode, profilerUrl, controller, route, template, formTypes.
hash,method,url,statusCode,profilerUrl,controller,route,template,formTypes
18e6b8,GET,http://127.0.0.1:8000/user/1,200,_profiler/18e6b8,App\Controller\UserController::show,user_show,user/show.html.twig,2026-01-11
Lists all Symfony console commands available in the project. This MCP tool provides access to configured console commands with their class names and file paths.
The tool returns CSV format with columns: name, className, filePath.
name,className,filePath
cache:clear,\App\Command\CacheClearCommand,src/Command/CacheClearCommand.php
doctrine:fixtures:load,\Doctrine\Bundle\FixturesBundle\Command\LoadDataFixturesDoctrineCommand,vendor/doctrine/doctrine-fixtures-bundle/Command/LoadDataFixturesDoctrineCommand.php2026-01-11
Lists all fields of a Doctrine entity as CSV. This MCP tool provides detailed field information for a specific entity class including field names, column names, types, and relations.
The tool returns CSV format with columns: name, column, type, relation, relationType.
name,column,type,relation,relationType
id,id,integer,,
username,username,string,,
email,email,string,,
orders,orders,,App\Entity\Order,OneToMany2026-01-11
Lists all Doctrine ORM entities in the project as CSV. This MCP tool provides access to all configured Doctrine entities with their class names and file paths.
The tool returns CSV format with columns: className, filePath.
className,filePath
App\Entity\User,src/Entity/User.php
App\Entity\Product,src/Entity/Product.php
App\Entity\Order,src/Entity/Order.php2026-01-11
Lists all Symfony form types configured in the project. This MCP tool provides access to form type aliases, class names, and their file locations.
The tool returns CSV format with columns: name, className, filePath.
name,className,filePath
user,App\Form\UserType,src/Form/UserType.php
email,Symfony\Component\Form\Extension\Core\Type\EmailType,vendor/symfony/form/Extension/Core/Type/EmailType.php2026-01-11
Lists Symfony routes with their controller mappings and file paths. This MCP tool provides access to routes configured in the Symfony project with optional filtering by route name or controller.
The tool returns CSV format with columns: name, controller, path, filePath.
name,controller,path,filePath
app_home,App\Controller\HomeController::index,/,src/Controller/HomeController.php
api_users_list,App\Controller\UserController::list,/api/users,src/Controller/UserController.php
api_users_show,App\Controller\UserController::show,/api/users/{id},src/Controller/UserController.php2026-01-11
Matches a plain request URL to Symfony routes using reverse pattern matching. This MCP tool finds routes that could handle a given URL path by matching against route patterns with placeholders.
The tool returns CSV format with columns: name, controller, path, filePath.
name,controller,path,filePath
api_user_show,App\Controller\Api\UserController::show,/api/users/{id},src/Controller/Api/UserController.php
api_user_list,App\Controller\Api\UserController::list,/api/users,src/Controller/Api/UserController.php2026-01-11
Locates where a Symfony service is defined in configuration files by service name or class name. This MCP tool provides access to service definitions with their file paths and line numbers.
The tool returns CSV format with columns: serviceName, className, filePath, lineNumber.
serviceName,className,filePath,lineNumber
app.service.my_service,\App\Service\MyService,config/services.yaml,15
app.my_service_alias,\App\Service\MyService,config/services.yaml,252026-01-11
Lists available Twig template extensions for code generation and template assistance. This MCP tool provides unified access to all Twig extensions including filters, functions, tests, and tags.
The tool returns CSV format with columns: extension_type, name, className, methodName, parameters.
extension_type,name,className,methodName,parameters
filter,upper,\Twig\Extension\CoreExtension,upper,"value,encoding"
function,path,\Twig\Extension\AssetExtension,path,"url,name"
filter,date,\Twig\Extension\CoreExtension,date,"date,format"2026-01-09
Reports empty #[ORM\Table] attributes on Doctrine entities. An empty Table attribute (with no arguments) provides no additional configuration beyond the default table name and can be safely removed. The inspection only reports when an Entity attribute is also present on the class.
Before:
use Doctrine\ORM\Mapping as ORM;
#[ORM\Entity]
#[ORM\Table] class Product
{
// ...
}After:
use Doctrine\ORM\Mapping as ORM;
#[ORM\Entity]
class Product
{
// ...
}Table attribute is only useful when you need custom configuration:
#[ORM\Entity]
#[ORM\Table(name: 'products', schema: 'app')]
class Product
{
// ...
}2026-01-08
Reports deprecated WITH usage in Doctrine ORM QueryBuilder join methods and DQL for arbitrary joins. Since Doctrine ORM 3.x, WITH should only be used for association joins (defined relations), while ON should be used for arbitrary joins (joins with entity class and join condition). The inspection only triggers when the Doctrine ORM version has this deprecation.
QueryBuilder - Before (Deprecated):
$qb->join(Partner::class, 'p', Expr\Join::WITH, 'p.id = u.myId');
$qb->leftJoin('App\Entity\Geo', 'g', 'WITH', 'g.id = u.geoId');QueryBuilder - After (Correct):
$qb->join(Partner::class, 'p', Expr\Join::ON, 'p.id = u.myId');
$qb->leftJoin('App\Entity\Geo', 'g', 'ON', 'g.id = u.geoId');DQL - Before (Deprecated):
$em->createQuery('SELECT u FROM User u JOIN Banlist b WITH u.email = b.email');
$em->createQuery('SELECT u, p FROM User u JOIN ' . CmsPhonenumber::class . ' p WITH u = p.user');DQL - After (Correct):
$em->createQuery('SELECT u FROM User u JOIN Banlist b ON u.email = b.email');
$em->createQuery('SELECT u, p FROM User u JOIN ' . CmsPhonenumber::class . ' p ON u = p.user');Association joins (WITH is still valid):
// No warning - this is an association join (u.orders has a defined relation)
$qb->join('u.orders', 'o', 'WITH', 'o.status = :status');