Issue with MCP Server Lifecycle: Manual restart required after config changes

[gopika_01]

I'm currently developing using MCP servers and hitting a significant friction point. Every time I update the configuration ( argument in the JSON), I have to manually quit and restart the host application to see the changes.

The Issue:

Lack of "Hot Reload" for MCP configurations.

Current workflow: Edit JSON -> Quit App -> Reopen App -> Wait for initialization.

[v-priyankata]

Hi  

Thank you for reaching out to the Microsoft Fabric Forum Community.

As a workaround, you could check whether your host application has an option to restart or reconnect MCP servers individually instead of restarting the entire app. If not, it may simply be that config changes like JSON argument updates are only picked up when the host reinitializes the MCP servers. For development, a practical way to reduce the friction is to limit frequent config edits where possible or automate the restart process to save time. If reloading MCP configurations isn’t currently supported, having a hot-reload or a simple 'Reload MCP Configuration' option would be a really helpful improvement.

If nothing works, Kindly raise a support ticket so the issue can be properly investigated by the product team:  Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn

If there are any deviations from your expectation please let us know we are happy to address.

Thanks.

[Sivapriya]

I also faced the same issue while building a tooling layer that reads and writes Power BI project (.pbip) files externally. The tools modify the report layout JSON  directly on disk . But the problem is Power BI Desktop does not detect or apply changes made to the underlying .pbip JSON files while the project is open