Open
Description
Check Existing Issues
- I have searched the existing issues and discussions.
Problem Description
Currently, changing the running MCPs requires the service to be killed and reloaded. Alternative clients are able to reload MCPs on changes (you can see how I implemented it for Roo Code here - RooCodeInc/Roo-Code#4267) and it allows for a smoother experience, especially when running MCPs that maintain a state or benefit from long running operation.
Desired Solution you'd like
Implement a hot reload mechanism that allows the service to pick up changes to a json config file and start only the child server, allowing for installation of new MCPs without interrupting existing operation.
Alternatives Considered
No response
Additional Context
This will allow for future improvements like automatic / one click installs or a management interface.