Jetbrains Symfony Support

What is included in Jetbrains Symfony Support?

Symfony Awareness – Completion and navigation for services, routes, Doctrine.
Twig Support – Completion, type resolution, and template navigation.
Symbol Navigation – Jump to controllers, routes, templates, and entities.
Deprecation Inspections – Flag outdated Doctrine and Symfony API usage.
Core Capacity – Supports Symfony 2 through current major releases.
Important – Requires PhpStorm or IntelliJ IDEA, not standalone.

What are the main benefits of Jetbrains Symfony Support?

Symfony Support is a PhpStorm and IntelliJ IDEA plugin that makes the IDE read a Symfony project the way the framework does, across PHP, Twig, YAML, and XML. It adds framework-aware completion, navigation, inspections, and code generation instead of treating Symfony configuration as plain text.

Faster Navigation – Gutter icons link controllers, routes, and templates.
Fewer Bugs – Inspections catch deprecated Doctrine and Symfony code.
Less Boilerplate – Intentions generate service definitions and inject dependencies.
Upgrade Safety – Warns about Doctrine ORM 3 and 4 removals.
Twig Accuracy – Resolves template variable types from controller renders.
AI Tooling – Exposes routes and commands as MCP tools.

What does the Symfony Support plugin do?

It teaches PhpStorm and IntelliJ IDEA to understand a Symfony project instead of seeing only generic PHP. The plugin indexes the service container, routes, Doctrine entities, Twig templates, and translations, then provides completion and one-click navigation between them — for example, jumping from a controller action to its Twig template through a gutter icon. It also runs framework-specific inspections that flag deprecated Doctrine and Symfony APIs while you type. Without it, the IDE treats container IDs, route names, and template paths as plain strings with no Symfony meaning.

Which Symfony features and versions does it support?

It supports Symfony 2, 3, 4, and the current major releases, working across the PHP, Twig, YAML, and XML files in a project. Beyond core framework support it handles Doctrine ORM mapping, the Form component, routing attributes, translations, and Symfony UX, including Twig Components, Live Components, and Stimulus controller completion. It also resolves Twig variable types passed from controller render calls, so template completion reflects the actual objects you rendered. That awareness of the service container and Twig context is what plain PHP assistance cannot provide.

What is the difference between the free plugin and the paid license?

Since PhpStorm 2022.1 the plugin is freemium: the open-source feature set is free, and a paid license enables the premium features marked as paid in the changelog. Premium adds advanced inspections — such as Doctrine ORM deprecation checks and autowiring or constructor-misuse warnings — plus Full Line Completion that can inject a service through a property or complete Doctrine QueryBuilder joins. After a project opens there is roughly a 15-minute grace period in which all premium features work, so you can trial them before buying. Core completion, navigation, and Twig support stay available even without a license.

Do I still need PhpStorm to use this plugin?

Yes — Symfony Support is an IDE plugin, not a standalone application, so it only runs inside PhpStorm or IntelliJ IDEA Ultimate with PHP support enabled. It is also not bundled with PhpStorm; you install it from the JetBrains Marketplace and enable it per project under the PHP settings. The license covers the plugin's premium features and does not include the JetBrains IDE itself, which is licensed separately. If you do not already work in a JetBrains PHP IDE, this add-on alone will not give you a working Symfony environment.

How does it help in day-to-day Symfony development?

It removes the manual lookups that slow Symfony work by connecting related files and generating wiring for you. A constructor-injection intention adds a missing service property, its constructor argument, and the import in one step, while the service-definition generator builds matching YAML, XML, or PHP config from a class. Deprecation inspections surface Doctrine ORM 3.0 and 4.0 removals — such as join-column or QueryBuilder changes — as you edit, instead of at runtime after an upgrade. For teams modernizing older Symfony code, those inline warnings turn a risky framework upgrade into a series of small, guided fixes.

Frequently asked questions about Jetbrains Symfony Support

Does Symfony Support include AI or MCP tooling?

Yes. The plugin registers Symfony-specific tools through JetBrains' MCP server toolset API, exposing project data such as routes, console commands, and Twig template variables to AI assistants in the IDE. The route tool returns the URL, controller, file path, line number, and rendered template in a single lookup, and supports Ant-style file-glob filters to scope large projects. This lets an assistant move from a request URL to the exact controller and template without separate searches.

Does it keep up with new Symfony and Doctrine releases?

Yes. The plugin is actively maintained and ships new inspections as the frameworks change — recent ones target Doctrine ORM 4.0 mapping changes and the deprecation of Symfony's Bundle registerCommands() hook in Symfony 8.1. Because deprecation checks track current releases, the plugin is most useful to teams that upgrade regularly and want warnings before a version jump rather than after it.