💡 Something we’ve been brainstorming: What if mcpservers lived in the extra section of composer.json and PhpStorm picked them up automatically? Good? Bad? Totally wrong direction?
@phpstorm As composer.json is PHP specific and nowadays people in teams use different editors / tools it's better to rely on .mcp.json or sth more generic as MCP is not PHP thing (as composer.json is).
@phpstorm Instead of bringing new stuff, what about fixing the stuff you broke??? 😡👿🤬 youtrack.jetbrains.com/issue/IJPL-201… youtrack.jetbrains.com/issue/IJPL-200… youtrack.jetbrains.com/issue/IJPL-200…
@phpstorm Given the previous discussions, a `[.]mcp.json` at project root would be ideal as it is not IDE-specific. Others IDEs could add support for this file, or users could create symbolic link to it
@phpstorm Something in the composer file for packages so we have a standard why of exposing them and then something in the .idea directory to utilise them per project/environment. Bonus points if we get to expose/register globally via composer?