Skip to content

Conversation

@PanchoDP
Copy link
Contributor

Problem Details

Before:
User selects:
☑ PhpStorm (MCP Client)
☐ Junie (Agent)

Result: Creates .junie/mcp/mcp.json
Problem: .junie directory created unnecessarily

Now:
User selects:
☑ PhpStorm (MCP Client)
☐ Junie (Agent)

Result: Creates .idea/mcp.json
Benefit: .junie only created when actually needed

Benefits Summary

  • Cleaner: Doesn't create unnecessary directories in the project
  • More logical: .junie only exists when Junie is active
  • Better organization: Uses PhpStorm's native structure (.idea/) when appropriate
  • Maintains compatibility: When Junie is an agent, still uses .junie/mcp/

@pushpak1300 pushpak1300 self-requested a review December 24, 2025 06:45
@pushpak1300
Copy link
Member

@PanchoDP Right now in PhpStorm there are two agents: the AI Assistant and Junie. Boost currently supports only the Junie MCP config. Earlier, the AI Assistant did not support project level MCP configuration, so we did not add support for it.

Recently, in the new PhpStorm version, JetBrains changed the MCP config location and merged both the AI Assistant and Junie into a single setup. The new location is .ai/mcp/mcp.json as described here: https://blog.jetbrains.com/phpstorm/2025/12/phpstorm-2025-3-is-now-out/

That said, we still need to support older PhpStorm versions that rely on the Junie config. Adding this change now would likely introduce more issues until there is a clear and proper upgrade path. Because of that, it does not really make sense to add this change at the moment as current junie config still supported in new MCP.

@PanchoDP
Copy link
Contributor Author

Thanks Pushpak!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants