Support multiple config directories for a client #84
Conversation
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
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.
What I did
Note: Open for a discussion on whether we should even support this feature given it's coming from a single client at the moment.
Handling a request from a LM Studio folks (we have them listed as a client) to support multiple mcp.json config paths. They mentioned that users who started using their app long time ago would have their mcp servers config file in
~/.cache/lm-studio/mcp.jsonrather than in~/.lmstudio/mcp.jsonfor new users. This PR tries to handle both scenarios.Slack thread for more context
Related issue
(not mandatory) A picture of a cute animal, if possible in relation to what you did