Read the standard mcp_config_path config key for Junie instead of the never-documented mcp_path - #995
Merged
pushpak1300 merged 1 commit intoSep 3, 2026
Conversation
… never-documented mcp_path
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Junie is the only agent reading its mcp path from boost.agents.junie.mcp_path, the other 11 agents all read mcp_config_path. so anyone overriding junie the way every other agent works gets silently ignored and the file always lands at the default .junie/mcp/mcp.json
tried it on a fresh app with boost.agents.junie.mcp_config_path set to .junie/custom/mcp.json, on main boost:install --mcp ignores it and writes .junie/mcp/mcp.json, with this change it writes .junie/custom/mcp.json
one line, just renames the key to match the rest
re-file of #967, reviewed and re-tested individually